break_execution · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What break_execution does on MCP Debug Server

AI agents invoke break_execution to trigger actions in MCP Debug Server. 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 break_execution needs a policy

This tool pauses a running process by breaking into the debugger, which is an external operation that affects process execution state. It does not delete data (not Destructive) or move money (not Financial), but it does trigger an external operation — interrupting a live process — whose impact depends on the target process. Misuse could cause service disruption or denial of service on critical processes.

From the tool's definition Break into debugger (pause process execution)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

break_execution Rate-limited

break_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": {
    "break_execution": {
      "limits": [
        {
          "counter": "break_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 Debug Server, so you can run agents against it safely.

FAQ

Questions about break_execution

What does the break_execution tool do? +

Break into debugger (pause process execution). It is categorised as a Execute tool in the MCP Debug Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on break_execution? +

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

What risk level is break_execution? +

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

Can I rate-limit break_execution? +

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

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

break_execution is provided by the MCP Debug Server MCP server (nickzer0/mcp-debugserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.