AI agents use lldb_set_breakpoint to create or update resources in LLDB-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLDB-MCP environment.
Setting a breakpoint modifies the debug state of a running process by inserting a breakpoint at a specified location. This is a reversible write operation (breakpoints can be removed, as evidenced by the sibling tool lldb_breakpoint_delete). It does not execute code, delete data, or involve finances.
From the tool's definition Tool name: lldb_set_breakpoint, description: 'Set a breakpoint'
Documented attack patterns abuse exactly the kind of access lldb_set_breakpoint 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_set_breakpoint:
{
"version": "1",
"default": "deny",
"tools": {
"lldb_set_breakpoint": {
"limits": [
{
"counter": "lldb_set_breakpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lldb_set_breakpoint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set a breakpoint. It is categorised as a Write tool in the LLDB-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LLDB- MCP server in PolicyLayer and add a rule for lldb_set_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 LLDB-MCP. Nothing to install.
lldb_set_breakpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lldb_set_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 lldb_set_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.
lldb_set_breakpoint 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.