Clear all breakpoints at once. Use this after verifying the root cause to clean up before moving on to the next task.
AI agents call clear_all_breakpoints to permanently remove resources in DebugMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing all breakpoints at once is an irreversible bulk deletion of debugging state. While breakpoints can technically be re-added manually, the action itself cannot be undone automatically and destroys all configured breakpoints in one operation. The blast radius is medium — misuse disrupts an active debugging session and loses all breakpoint configurations, but does not affect source code or persistent data.
From the tool's definition Clear all breakpoints at once
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access clear_all_breakpoints gives an agent:
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 clear_all_breakpoints:
{
"version": "1",
"default": "deny",
"hide": [
"clear_all_breakpoints"
]
}clear_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.
Free to start. No card required.
Clear all breakpoints at once. Use this after verifying the root cause to clean up before moving on to the next task. 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.
Register the Debug MCP server in PolicyLayer and add a rule for clear_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 DebugMCP. Nothing to install.
clear_all_breakpoints is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_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.
Set action: deny in the PolicyLayer policy for clear_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.
clear_all_breakpoints 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.
Start from DebugMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 DebugMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.