Low Risk

bins

Examine available chunks with pwndbg command bins

How to control bins ↓

AI agents call bins 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 tool queries heap metadata to display available memory chunks, a passive reconnaissance operation typical of debuggers. It has no side effects, does not execute code, and does not modify the debugged process. The low severity reflects that while an agent could gather information about heap layout, this alone causes no harm and is consistent with standard debugging workflows.

From the tool's definition Tool name 'bins' and description 'Examine available chunks with pwndbg command bins' indicate read-only inspection of memory heap chunks. The verb 'examine' and 'pwndbg command' context show this retrieves debugging information without modifying state.

Documented attack patterns abuse exactly the kind of access bins 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 bins:

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

bins 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 bins tool do? +

Examine available chunks with pwndbg command bins. 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 bins? +

Register the Pwndbg MCP server in PolicyLayer and add a rule for bins: 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 bins? +

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

Can I rate-limit bins? +

Yes. Add a rate_limit block to the bins 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 bins completely? +

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

bins 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.