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 invoke dbg_goto to trigger actions in Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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 High
This tool manipulates the execution flow of a running/paused program by moving the program counter, causing code to be skipped or repeated. While labeled 'DESTRUCTIVE' in the description, the actual destructive aspect is that it irreversibly alters execution flow rather than deleting data. It is best classified as Execute since it triggers external program execution behavior.
From the tool's definition Move the program counter within the current stopped frame — 'set next statement' (DAP gotoTargets + goto)... DESTRUCTIVE: skips or repeats code by moving execution
Risk signalsAccepts file system path (path)
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 stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
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. Only meaningful while stopped at a breakpoint. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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