Critical Risk →

debugger_remove_breakpoint

Remove a breakpoint from the debug session.

Part of the Mcp Debugger MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call debugger_remove_breakpoint to permanently remove or destroy resources in Mcp Debugger. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call debugger_remove_breakpoint in a loop, permanently destroying resources in Mcp Debugger. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-digital-defiance-mcp-debugger.yaml
tools:
  debugger_remove_breakpoint:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Debugger policy for all 29 tools.

Tool Name debugger_remove_breakpoint
Category Destructive
Risk Level Critical

View all 29 tools →

Agents calling destructive-class tools like debugger_remove_breakpoint have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

debugger_remove_breakpoint is one of the critical-risk operations in Mcp Debugger. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the debugger_remove_breakpoint tool do? +

Remove a breakpoint from the debug session.. It is categorised as a Destructive tool in the Mcp Debugger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on debugger_remove_breakpoint? +

Add a rule in your Intercept YAML policy under the tools section for debugger_remove_breakpoint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Debugger MCP server.

What risk level is debugger_remove_breakpoint? +

debugger_remove_breakpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit debugger_remove_breakpoint? +

Yes. Add a rate_limit block to the debugger_remove_breakpoint rule in your Intercept 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 debugger_remove_breakpoint completely? +

Set action: deny in the Intercept policy for debugger_remove_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 debugger_remove_breakpoint? +

debugger_remove_breakpoint is provided by the Mcp Debugger MCP server (@ai-capabilities-suite/mcp-debugger-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Debugger

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.