pwndbg_cpsr
AI agents call pwndbg_cpsr 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.
CPSR/PSTATE reads are non-destructive introspection operations on a debugged process. While the tool description is empty (lowering confidence slightly), the tool name and sibling tools strongly suggest this retrieves CPU register state information. In a debugging context, reading registers has minimal blast radius—it gathers information about the target process but cannot modify code, memory, or system state.
From the tool's definition Tool name 'pwndbg_cpsr' and server context indicate this reads the CPSR (Current Program Status Register) in ARM debugging, consistent with other pwndbg read tools like 'pwndbg_backtrace', 'pwndbg_auxv', and 'pwndbg_argc' which query debugger state without…
Attacks that exploit this kind of access
pwndbg_cpsr. 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_cpsr: 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_cpsr 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_cpsr 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_cpsr. 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_cpsr 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 →