Clear breakpoints from file or all files.
AI agents call debug_clear_breakpoints to permanently remove resources in Polybugger — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing breakpoints removes debugging configuration that may have been carefully set up. The 'all files' scope makes this potentially irreversible at scale (no indication of undo/restore). While not deleting user data or code, it destroys debugging session state which could disrupt active debugging workflows and is not easily recoverable without re-adding each breakpoint manually.
From the tool's definition 'Clear breakpoints from file or all files' — irreversibly removes breakpoint configuration data, with 'all files' option having broad blast radius
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear breakpoints from file or all files. It is categorised as a Destructive tool in the Polybugger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Polybugger MCP server in PolicyLayer and add a rule for debug_clear_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 Polybugger. Nothing to install.
debug_clear_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 debug_clear_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 debug_clear_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.
debug_clear_breakpoints is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →