pwndbg_run_until_stop
AI agents invoke pwndbg_run_until_stop to trigger actions in Pwndbg Lldb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes debugger control flow operations that trigger external code execution within a target binary. While debugging is intentional, an AI agent could misuse it to execute arbitrary or sensitive code paths in the debugged process, potentially with unintended side effects.
From the tool's definition Tool name 'pwndbg_run_until_stop' indicates it controls debugger execution flow (run/resume until a breakpoint or stop condition). Description is empty, but context shows this is a pwndbg command exposed as a debugging tool under LLDB.
Attacks that exploit this kind of access
pwndbg_run_until_stop. It is categorised as a Execute tool in the Pwndbg Lldb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pwndbg Lldb MCP server in PolicyLayer and add a rule for pwndbg_run_until_stop: 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_run_until_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pwndbg_run_until_stop 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_run_until_stop. 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_run_until_stop 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 →