run_python

Run a short Python snippet in a temp file and return its stdout/stderr.

SERVERMcp Hands SOURCEhuocai250/mcp-hands

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-hands/run-python.md

WHAT IT DOES

What run_python does on Mcp Hands

AI agents invoke run_python to trigger actions in Mcp Hands. 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.

RISK

Why run_python is rated High

run_python triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_python safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Hands, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_python, this is the rule to start with:

run_python Rate-limited

run_python 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": {
    "run_python": {
      "limits": [
        {
          "counter": "run_python_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Hands, apply this rule, and every run_python call is checked against it from then on.

FAQ

Questions about run_python

What does the run_python tool do? +

Run a short Python snippet in a temp file and return its stdout/stderr. It is categorised as a Execute tool in the Mcp Hands MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_python? +

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

What risk level is run_python? +

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

Can I rate-limit run_python? +

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

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

run_python is provided by the Mcp Hands MCP server (huocai250/mcp-hands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Hands, and thousands of servers like it.

This server

All 378 Mcp Hands tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →