AI agents call lldb_breakpoint_delete to permanently remove resources in LLDB-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a breakpoint is an irreversible action within the debugging session; once removed, the breakpoint configuration is lost and execution will no longer pause at that location. While the blast radius is limited to the debug session (not production data), it fits the Destructive category as it cannot be undone without manual re-creation.
From the tool's definition 'Delete a breakpoint' — the tool irreversibly removes a breakpoint from the debugging session
Documented attack patterns abuse exactly the kind of access lldb_breakpoint_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLDB-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for lldb_breakpoint_delete:
{
"version": "1",
"default": "deny",
"hide": [
"lldb_breakpoint_delete"
]
}lldb_breakpoint_delete 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.
Delete a breakpoint. It is categorised as a Destructive tool in the LLDB-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LLDB- MCP server in PolicyLayer and add a rule for lldb_breakpoint_delete: 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 LLDB-MCP. Nothing to install.
lldb_breakpoint_delete 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 lldb_breakpoint_delete 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 lldb_breakpoint_delete. 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.
lldb_breakpoint_delete is provided by the LLDB- MCP server (stass/lldb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 LLDB-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 LLDB-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.