Print the argument count (argc) of the running program.
AI agents call pwndbg_argc 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 reads and displays the argc value from the debugged process's memory or runtime state. It performs no writes, deletions, code execution, or state changes. It is purely informational, similar to inspecting a variable in a debugger. The low severity reflects that reading argc poses minimal risk—it cannot alter the program state or cause unintended effects through misuse.
From the tool's definition Tool name 'pwndbg_argc' and description 'Print the argument count (argc) of the running program' indicate a read-only query operation that retrieves program state information without modification or side effects.
Attacks that exploit this kind of access
Print the argument count (argc) of the running program. 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_argc: 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_argc 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_argc 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_argc. 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_argc 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 →