run_python_file · MCP Python Interpreter MCP: Risk & Policy

WHAT IT DOES

What run_python_file does on MCP Python Interpreter

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

Running arbitrary Python files is code execution with side effects dependent on file contents and arguments. The blast radius is high: an agent could execute malicious code, modify system state, exfiltrate data, or trigger unintended operations.

From the tool's definition Tool named 'run_python_file' on a server that 'Enables LLMs to interact with Python environments, execute code' — the description explicitly states execution capability. Sibling tool 'run_python_code' confirms the server's execution focus.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_python_file Rate-limited

run_python_file 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_file": {
      "limits": [
        {
          "counter": "run_python_file_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 MCP Python Interpreter, so you can run agents against it safely.

FAQ

Questions about run_python_file

What does the run_python_file tool do? +

run_python_file. It is categorised as a Execute tool in the MCP Python Interpreter 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_file? +

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

What risk level is run_python_file? +

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

Can I rate-limit run_python_file? +

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

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

run_python_file is provided by the MCP Python Interpreter MCP server (luutuankiet/mcp-python-interpreter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.