debug_continue · Polybugger MCP: Risk & Policy

WHAT IT DOES

What debug_continue does on Polybugger

AI agents invoke debug_continue to trigger actions in Polybugger. 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 IT NEEDS A POLICY

Why debug_continue needs a policy

This tool resumes program execution in a debugger, which causes code to run until the next breakpoint or program termination. It directly triggers execution of arbitrary code in the debugged process, placing it in the Execute category. Severity is medium because misuse could cause a paused program to run unintended code paths, but it operates within an already-running debug session context.

From the tool's definition Continue until next breakpoint or end — resumes execution of a paused debug session, triggering further code execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_continue Rate-limited

debug_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_continue": {
      "limits": [
        {
          "counter": "debug_continue_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Polybugger, so you can run agents against it safely.

FAQ

Questions about debug_continue

What does the debug_continue tool do? +

Continue until next breakpoint or end. It is categorised as a Execute tool in the Polybugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debug_continue? +

Register the Polybugger MCP server in PolicyLayer and add a rule for debug_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 Polybugger. Nothing to install.

What risk level is debug_continue? +

debug_continue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit debug_continue? +

Yes. Add a rate_limit block to the debug_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.

How do I block debug_continue completely? +

Set action: deny in the PolicyLayer policy for debug_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.

What MCP server provides debug_continue? +

debug_continue is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.