install_python_library · Simple MCP: Risk & Policy

WHAT IT DOES

What install_python_library does on Simple MCP

AI agents invoke install_python_library to trigger actions in Simple MCP. 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 install_python_library needs a policy

Installing a Python library executes a system command (such as pip) that modifies the environment by adding software. This is an Execute-category action with high severity since an AI agent could install malicious or unwanted packages on the host system, potentially compromising security or stability. The empty description lowers confidence slightly, but the tool name strongly implies this behavior.

From the tool's definition Tool name 'install_python_library' implies installing software packages onto the system, which executes system-level package management commands (e.g., pip install). Description is empty, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_python_library Rate-limited

install_python_library 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": {
    "install_python_library": {
      "limits": [
        {
          "counter": "install_python_library_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 Simple MCP, so you can run agents against it safely.

FAQ

Questions about install_python_library

What does the install_python_library tool do? +

install_python_library. It is categorised as a Execute tool in the Simple MCP 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_library? +

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

What risk level is install_python_library? +

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

Can I rate-limit install_python_library? +

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

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

install_python_library is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.