dbg_goto
Move the program counter within the current stopped frame — 'set next statement' (DAP gotoTargets + goto). Call with path + line to list the valid goto targets on that line; when the line has exactly one target (or you pass target_id) it jumps there. DESTRUCTIVE: skips or repeats code by moving e...
This record as markdown: /tools/breakpoint-mcp/dbg-goto.md
What dbg_goto does on Breakpoint
AI agents call dbg_goto to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
line | integer | Yes | 1-based target line |
path | string | Yes | Script path (res://..., absolute, or project-relative) |
confirm | boolean | — | Auto-approve the jump (skip the confirmation prompt) |
target_id | integer | — | A specific target id from a prior dbg_goto listing; omit to auto-pick when the line has a single target |
Parameters from the server's own tool schema.
Why dbg_goto is rated Critical
An AI agent that decides to call dbg_goto doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Breakpoint is gone. There is no undo for destructive operations.
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs dbg_goto safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dbg_goto, this is the rule to start with:
dbg_goto is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every dbg_goto call is checked against it from then on.
Questions about dbg_goto
Move the program counter within the current stopped frame — 'set next statement' (DAP gotoTargets + goto). Call with path + line to list the valid goto targets on that line; when the line has exactly one target (or you pass target_id) it jumps there. DESTRUCTIVE: skips or repeats code by moving execution — confirm with the user and keep this gated. Feature-detected: on an adapter that does not advertise supportsGotoTargetsRequest it returns a clear "unsupported" message WITHOUT prompting. Measured: no Godot build this project tests advertises it — 4.3-stable and 4.7-stable both refuse this tool, so on a shipped engine it is unsupported surface today rather than a feature you can reach; see docs/dap_capability_ledger.json. It is kept, and kept guarded, because a capability is not a boundary and a build can start advertising it. Refuses a source that can never carry a target — a missing file, a directory, an empty path (which resolves to the project root), or a path resolving outside the Godot project root — the same guard dbg_set_breakpoints applies. Only meaningful while stopped at a breakpoint. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
dbg_goto accepts 4 parameters: line, path, confirm, target_id. Required: line, path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for dbg_goto: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Breakpoint. Nothing to install.
dbg_goto is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dbg_goto rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for dbg_goto. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
dbg_goto is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue