// MCP TOOL REFERENCE

install_python_packages

Install additional Python packages using the shared package manager (uv). Args: packages: Space-separated package list. upgrade: If True, perform upgrades when applicable.

ServerPwno
CategoryExecute

How to control install_python_packages ↓

WHAT INSTALL_PYTHON_PACKAGES ON PWNO DOES

AI agents invoke install_python_packages to trigger actions in Pwno. 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.

THE RISK

High Risk

Installing Python packages executes external operations (package manager invocations, network fetches, file system writes) that can introduce arbitrary code into the environment. This goes beyond a simple write—it triggers execution of install scripts and can affect system state. Not destructive by default, but misuse could introduce malicious packages.

From the tool's definition Install additional Python packages using the shared package manager (uv)

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

HOW TO CONTROL INSTALL_PYTHON_PACKAGES

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 install_python_packages:

policy.json

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

install_python_packages 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 pwncli_stop Stop a pwncli driver session and clear its session pipe. 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:

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

Install additional Python packages using the shared package manager (uv). Args: packages: Space-separated package list. upgrade: If True, perform upgrades when applicable. 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 install_python_packages? +

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

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

Can I rate-limit install_python_packages? +

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

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

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

install_python_packages

// WHAT INSTALL_PYTHON_PACKAGES ON PWNO DOES

// THE RISK

// HOW TO CONTROL INSTALL_PYTHON_PACKAGES

// EXPLORE