enable_breakpoint · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What enable_breakpoint does on MCP Debug Server

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

Enabling a breakpoint modifies the execution behavior of a running process by reactivating a previously disabled breakpoint. This is an Execute-category action as it directly controls and alters the execution flow of an external process. Misuse could interfere with production processes or cause instability, warranting medium severity.

From the tool's definition Enable a disabled breakpoint — activates a debugging control point that affects execution flow of an attached Windows process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_breakpoint Rate-limited

enable_breakpoint 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": {
    "enable_breakpoint": {
      "limits": [
        {
          "counter": "enable_breakpoint_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 enable_breakpoint

What does the enable_breakpoint tool do? +

Enable a disabled breakpoint. 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 enable_breakpoint? +

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

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

Can I rate-limit enable_breakpoint? +

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

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

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