set_exception_break · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What set_exception_break does on MCP Debug Server

AI agents invoke set_exception_break 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 set_exception_break needs a policy

Setting an exception breakpoint with auto-capture actively modifies the execution flow of a live Windows process being debugged. It installs hooks that intercept exceptions and trigger automated responses, which constitutes executing/controlling external process behavior. This can affect process stability and behavior in non-trivial ways, making misuse potentially high-impact.

From the tool's definition 'Set exception breakpoint with auto-capture' — sets breakpoints and triggers automatic capture behavior on exceptions in a live debugged process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_exception_break Rate-limited

set_exception_break 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": {
    "set_exception_break": {
      "limits": [
        {
          "counter": "set_exception_break_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 set_exception_break

What does the set_exception_break tool do? +

Set exception breakpoint with auto-capture. 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 set_exception_break? +

Register the MCP Debug Server MCP server in PolicyLayer and add a rule for set_exception_break: 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 set_exception_break? +

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

Can I rate-limit set_exception_break? +

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

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

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