List all breakpoints in the current session.
AI agents call pwndbg_breakpoint_list to retrieve information from Pwndbg Lldb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing breakpoint information from the debugging session. It performs no modifications, deletions, or execution of arbitrary code. It is a pure read operation analogous to listing or fetching data. The blast radius of misuse is minimal—an AI could only view breakpoint state, which poses no direct harm to the target system or data integrity.
From the tool's definition Tool name 'pwndbg_breakpoint_list' and description 'List all breakpoints in the current session' indicate a query/inspection operation with no side effects.
Attacks that exploit this kind of access
List all breakpoints in the current session. It is categorised as a Read tool in the Pwndbg Lldb MCP Server, which means it retrieves data without modifying state.
Register the Pwndbg Lldb MCP server in PolicyLayer and add a rule for pwndbg_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 Pwndbg Lldb. Nothing to install.
pwndbg_breakpoint_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pwndbg_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.
Set action: deny in the PolicyLayer policy for pwndbg_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.
pwndbg_breakpoint_list is provided by the Pwndbg Lldb MCP server (micro-evaluation-group/pwndbg-lldb-mcp). 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 →