Removes breakpoints. Pass breakpointId to remove a code breakpoint, url to remove an XHR breakpoint, or neither to remove ALL breakpoints (code + XHR).
AI agents call remove_breakpoint to permanently remove resources in JS Reverse MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing breakpoints, particularly all of them at once, is an irreversible action that destroys debugging state. While not as catastrophic as deleting data, the mass removal option ('neither to remove ALL breakpoints') can permanently disrupt an active debugging session with no undo mechanism, fitting the Destructive category over Write.
From the tool's definition 'remove ALL breakpoints (code + XHR)' — removing breakpoints is irreversible in the sense that the debugging state is permanently cleared without recovery, especially when 'neither' argument removes all breakpoints at once
Attacks that exploit this kind of access
Removes breakpoints. Pass breakpointId to remove a code breakpoint, url to remove an XHR breakpoint, or neither to remove ALL breakpoints (code + XHR). It is categorised as a Destructive tool in the JS Reverse MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JS Reverse 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 JS Reverse MCP. Nothing to install.
remove_breakpoint 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 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.
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.
remove_breakpoint is provided by the JS Reverse MCP server (zhizhuodemao/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.