Remove a breakpoint.
AI agents call remove_breakpoint to permanently remove resources in MCPEmulate — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call remove_breakpoint doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from MCPEmulate is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Remove a breakpoint. It is categorised as a Destructive tool in the MCPEmulate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCPEmulate 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 MCPEmulate. 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 MCPEmulate MCP server (labguy94/mcpemulate). 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 →