The debug query agent writes investigation SQL for an incident you are looking at. You describe what you want to know in plain language, and the agent reads the incident's context — the validator and its deviation, the source schema, catalog metadata — then drafts a query for that source's SQL dialect. The suggestion arrives as an unsaved draft in the Debug dialog, which you can edit, run, save, or discard like any other query.

The agent only writes SQL — it never runs it. Running a suggestion goes through the same debug query path as any other query, and still requires the sqlExecution:WRITE permission.