pwncli_stop

THE RISK

High Risk

This tool triggers an external operation that forcibly terminates a debugging session and clears associated pipes—these are side effects that cannot be controlled by parameter injection alone and depend on the current system state. While not destructive (no permanent data loss), it is an Execute action because it controls external process lifecycle.

From the tool's definition Tool performs session termination and resource cleanup ('Stop a pwncli driver session and clear its session pipe').

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

HOW TO CONTROL PWNCLI_STOP

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

policy.json

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

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

Create a free account and register Pwno — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Pwno tools

Execute execute execute Execute execute_python_code Execute Python code dynamically in the shared environment. Args: code Execute execute_python_script Execute an existing Python script within the shared environment. Args: Execute finish Run until the current function returns (MI -exec-finish). Execute run Run the loaded program under GDB control. Args: args: Argument string Execute run_command Execute a system command and wait for completion. Note: Use this for Execute spawn_process Spawn a long-running background process and return its PID and log paths. Note: Execute step_control Execute a stepping command (c, n, s, ni, si). Args: command: One of {

All 36 Pwno tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Pwno → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the pwncli_stop tool do? +

Stop a pwncli driver session and clear its session pipe. It is categorised as a Execute tool in the Pwno MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pwncli_stop? +

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

What risk level is pwncli_stop? +

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

Can I rate-limit pwncli_stop? +

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

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

pwncli_stop is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pwno tool call.

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

GOVERN PWNO →

Free to start. No card required.

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

// WHAT PWNCLI_STOP ON PWNO DOES

// THE RISK

// HOW TO CONTROL PWNCLI_STOP

// EXPLORE