AI agents call delete_breakpoint to permanently remove resources in MCP NodeJS Debugger — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly removes a breakpoint from the debugger. While the blast radius is low (breakpoints can be re-added manually), the action is a deletion and cannot be automatically undone, placing it in the Destructive category. Misuse could disrupt debugging sessions but has no broader system impact.
From the tool's definition 'delete_breakpoint' and 'Deletes a specified breakpoint'
Documented attack patterns abuse exactly the kind of access delete_breakpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP NodeJS Debugger, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_breakpoint:
{
"version": "1",
"default": "deny",
"hide": [
"delete_breakpoint"
]
}delete_breakpoint 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.
Deletes a specified breakpoint. It is categorised as a Destructive tool in the MCP NodeJS Debugger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP NodeJS Debugger MCP server in PolicyLayer and add a rule for delete_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 MCP NodeJS Debugger. Nothing to install.
delete_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 delete_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 delete_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.
delete_breakpoint is provided by the MCP NodeJS Debugger MCP server (workbackai/mcp-nodejs-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 MCP NodeJS Debugger tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 MCP NodeJS Debugger tools catalogued and risk-classified — across an index of 42,500+ MCP servers.