Evaluate an expression in the current frame (LLDB native).
AI agents invoke pwndbg_expression 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.
Evaluating an expression in a debugger frame is an Execute-class operation. LLDB expression evaluation can run arbitrary code in the context of the debugged process, including function calls, memory writes, and side effects. This goes beyond simply reading data — it actively executes code within the target process, making it high severity due to potential for arbitrary code execution and process state modification.
From the tool's definition Evaluate an expression in the current frame (LLDB native)
Attacks that exploit this kind of access
Evaluate an expression in the current frame (LLDB native). 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_expression: 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_expression 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_expression 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_expression. 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_expression 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 →