remove_all_breakpoints

THE RISK

Critical Risk

Why remove_all_breakpoints needs a policy

This tool irreversibly removes all breakpoints at once, which is a bulk destructive operation that cannot be easily undone (breakpoints would need to be manually re-added). While it doesn't delete files or data, it permanently removes debug configuration state in a non-reversible bulk action.

From the tool's definition Remove all breakpoints currently set in the debugger

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

POLICY

How to control remove_all_breakpoints

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

policy.json

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

remove_all_breakpoints 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 Dap — 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 Dap tools

Destructive terminate Terminate the current debugging session. Execute launch Launch the debuggee program. Set breakpoints before launching if necessary. Execute change_frame Change the current debugging frame to the specified frame ID. Execute continue_execution Continue execution in the debugger after hitting a breakpoint. Execute evaluate Evaluate an expression in the current debugging context. Execute next Step over to the next line of code in the debugger. Execute step_in Step into the function call in the debugger. Execute step_out Step out of the current function in the debugger.

All 14 Dap 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 Dap → 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_all_breakpoints

What does the remove_all_breakpoints tool do? +

Remove all breakpoints currently set in the debugger. It is categorised as a Destructive tool in the Dap 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_all_breakpoints? +

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

What risk level is remove_all_breakpoints? +

remove_all_breakpoints 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_all_breakpoints? +

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

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

remove_all_breakpoints is provided by the Dap MCP server (kashuncheng/dap_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dap tool call.

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

CHECK YOUR STACK →