remove_breakpoint

THE RISK

Critical Risk

Why remove_breakpoint needs a policy

Removing a breakpoint is an irreversible deletion of a debugging configuration. However, the blast radius is very low since breakpoints are lightweight debugging aids with no impact on production data or systems; the worst case is losing a debugging marker that would need to be re-added manually.

From the tool's definition 'Remove a breakpoint that is no longer needed' — permanently removes a debugging breakpoint

Documented attack patterns abuse exactly the kind of access remove_breakpoint gives an agent:

POLICY

How to control remove_breakpoint

PolicyLayer is an MCP gateway — it sits between your AI agents and DebugMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_breakpoint:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_breakpoint"
  ]
}

remove_breakpoint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register DebugMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DebugMCP tools

Destructive clear_all_breakpoints Clear all breakpoints at once. Use this after verifying the root cause to clean up before Execute continue_execution Resume program execution until the next breakpoint is hit or the program completes. Execute evaluate_expression Powerful runtime expression evaluator: Test hypotheses, check computed values, call method Execute restart_debugging Restart the debug session from the beginning with the same configuration. Execute start_debugging Start a VS Code debug session for a source file, optionally for a single test method. Execute step_into Dive into the current line of code. Execute step_out Step out of the current function Execute step_over Execute the current line of code without diving into it.

All 13 DebugMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in DebugMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_breakpoint

What does the remove_breakpoint tool do? +

Remove a breakpoint that is no longer needed. It is categorised as a Destructive tool in the DebugMCP 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 remove_breakpoint? +

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

What risk level is remove_breakpoint? +

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 remove_breakpoint? +

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

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

remove_breakpoint is provided by the Debug MCP server (microsoft/debugmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DebugMCP tool call.

Start from DebugMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →