manage-breakpoints · Debugger MCP Server MCP: Risk & Policy

WHAT IT DOES

What manage-breakpoints does on Debugger MCP Server

AI agents invoke manage-breakpoints to trigger actions in Debugger MCP 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 manage-breakpoints needs a policy

Managing breakpoints is not a pure read operation; setting or removing breakpoints modifies the execution behavior of a running program. This constitutes triggering external operations (in the Chrome DevTools/debugger context) that affect how code runs. While not destructive or financial, it is an Execute-level action due to its effect on runtime behavior.

From the tool's definition 'Set, remove, list, and manage breakpoints for debugging' — setting and removing breakpoints triggers active changes in the debugger runtime, affecting execution flow of the target application

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage-breakpoints Rate-limited

manage-breakpoints 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": {
    "manage-breakpoints": {
      "limits": [
        {
          "counter": "manage-breakpoints_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 Debugger MCP Server, so you can run agents against it safely.

FAQ

Questions about manage-breakpoints

What does the manage-breakpoints tool do? +

Set, remove, list, and manage breakpoints for debugging. It is categorised as a Execute tool in the Debugger MCP 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 manage-breakpoints? +

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

What risk level is manage-breakpoints? +

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

Can I rate-limit manage-breakpoints? +

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

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

manage-breakpoints is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.