Low Risk

lldb_breakpoint_list

List all breakpoints

How to control lldb_breakpoint_list ↓

AI agents call lldb_breakpoint_list to retrieve information from LLDB-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves existing breakpoint information from the debugger. It performs no modifications, does not execute code, and has no destructive or financial implications. While it is part of a debugging framework that could be misused in a broader attack, the tool itself is purely informational retrieval.

From the tool's definition Tool name 'lldb_breakpoint_list' and description 'List all breakpoints' indicate a query operation that retrieves debugging state without modification or side effects.

Documented attack patterns abuse exactly the kind of access lldb_breakpoint_list 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_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lldb_breakpoint_list": {}
  }
}

lldb_breakpoint_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LLDB-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the lldb_breakpoint_list tool do? +

List all breakpoints. It is categorised as a Read tool in the LLDB-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lldb_breakpoint_list? +

Register the LLDB- MCP server in PolicyLayer and add a rule for lldb_breakpoint_list: 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.

What risk level is lldb_breakpoint_list? +

lldb_breakpoint_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lldb_breakpoint_list? +

Yes. Add a rate_limit block to the lldb_breakpoint_list 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.

How do I block lldb_breakpoint_list completely? +

Set action: deny in the PolicyLayer policy for lldb_breakpoint_list. 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.

What MCP server provides lldb_breakpoint_list? +

lldb_breakpoint_list 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.

Enforce policy on every LLDB-MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.