continue_execution · Mcp Debugger MCP: Risk & Policy

WHAT IT DOES

What continue_execution does on Mcp Debugger

AI agents invoke continue_execution to trigger actions in Mcp Debugger. 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 continue_execution needs a policy

This tool resumes execution of a paused/stopped process in a debug session. It triggers external program execution, which classifies it as Execute. Misuse could cause unintended code to run in the attached process, but it does not inherently delete data or move money.

From the tool's definition Tool name: 'continue_execution'; description: 'Continue execution'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

continue_execution Rate-limited

continue_execution 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": {
    "continue_execution": {
      "limits": [
        {
          "counter": "continue_execution_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 Mcp Debugger, so you can run agents against it safely.

FAQ

Questions about continue_execution

What does the continue_execution tool do? +

Continue execution. It is categorised as a Execute tool in the Mcp Debugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on continue_execution? +

Register the Mcp Debugger MCP server in PolicyLayer and add a rule for continue_execution: 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 Mcp Debugger. Nothing to install.

What risk level is continue_execution? +

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

Can I rate-limit continue_execution? +

Yes. Add a rate_limit block to the continue_execution 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 continue_execution completely? +

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

continue_execution is provided by the Mcp Debugger MCP server (@debugmcp/mcp-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.