Low Risk

pwndbg_status

Return GDB status and additional GDB messages if some new messages

How to control pwndbg_status ↓

AI agents call pwndbg_status to retrieve information from Pwndbg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This is a read-only tool that retrieves debugging state information. However, the severity is elevated to medium rather than low because the tool operates within a debugger context where an agent could use status information to inform decisions about inspecting sensitive memory, registers containing credentials or keys, or other runtime data.

From the tool's definition Tool returns GDB status and messages, performing a query operation with no data modification. Name and description indicate it 'Return[s]' information without side effects.

Documented attack patterns abuse exactly the kind of access pwndbg_status gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Pwndbg, and nothing reaches the server without passing your rules. This is the rule we recommend for pwndbg_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pwndbg_status": {}
  }
}

pwndbg_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pwndbg — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the pwndbg_status tool do? +

Return GDB status and additional GDB messages if some new messages. It is categorised as a Read tool in the Pwndbg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pwndbg_status? +

Register the Pwndbg MCP server in PolicyLayer and add a rule for pwndbg_status: 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. Nothing to install.

What risk level is pwndbg_status? +

pwndbg_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pwndbg_status? +

Yes. Add a rate_limit block to the pwndbg_status 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.

How do I block pwndbg_status completely? +

Set action: deny in the PolicyLayer policy for pwndbg_status. 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.

What MCP server provides pwndbg_status? +

pwndbg_status is provided by the Pwndbg MCP server (rocketmadev/pwndbg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pwndbg tool call.

Deterministic rules across all 17 Pwndbg tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

17 Pwndbg tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.