pwndbg_run · Pwndbg Lldb MCP: Risk & Policy

WHAT IT DOES

What pwndbg_run does on Pwndbg Lldb

AI agents invoke pwndbg_run 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.

WHY IT NEEDS A POLICY

Why pwndbg_run needs a policy

The tool enables execution of code or binaries through a debugger, with outcomes dependent on what binary is loaded and what arguments/breakpoints are configured. This is Execute rather than Read because it actively runs code whose effects depend on the loaded binary and debugging state.

From the tool's definition Tool name 'pwndbg_run' indicates execution of debugged programs or debug commands within pwndbg/LLDB context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pwndbg_run Rate-limited

pwndbg_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pwndbg_run": {
      "limits": [
        {
          "counter": "pwndbg_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pwndbg Lldb, so you can run agents against it safely.

FAQ

Questions about pwndbg_run

What does the pwndbg_run tool do? +

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

How do I enforce a policy on pwndbg_run? +

Register the Pwndbg Lldb MCP server in PolicyLayer and add a rule for pwndbg_run: 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.

What risk level is pwndbg_run? +

pwndbg_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pwndbg_run? +

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

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

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