dbg_continue
Resume execution and wait for the program to settle again (next breakpoint or termination). Returns the resulting state; if it runs on with no further breakpoint, reports state 'running'.
This record as markdown: /tools/breakpoint-mcp/dbg-continue.md
What dbg_continue does on Breakpoint
AI agents invoke dbg_continue 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.
Why dbg_continue is rated High
This tool resumes execution of a running program, which is an external operation that triggers code execution. Misuse could cause unintended code paths to run, bypass breakpoints, or allow a program in a sensitive state to continue executing with unpredictable effects.
From the tool's definition Resume execution and wait for the program to settle again (next breakpoint or termination)
Attacks that exploit this kind of access
The rule that runs dbg_continue 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_continue, this is the rule to start with:
dbg_continue 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_continue call is checked against it from then on.
Questions about dbg_continue
Resume execution and wait for the program to settle again (next breakpoint or termination). Returns the resulting state; if it runs on with no further breakpoint, reports state 'running'. 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.
Register the Breakpoint MCP server in PolicyLayer and add a rule for dbg_continue: 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_continue 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_continue 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_continue. 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_continue 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