Run Python code in the current environment.
AI agents invoke run_python_code to trigger actions in Python Code Runner. 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.
This tool executes arbitrary Python code whose effects are entirely dependent on what code is provided as arguments. While the server claims a 'safe environment', execution of code is inherently an Execute-category action with potentially high blast radius if an AI agent misuses it to run malicious or unintended code, install unauthorized packages, or access/modify system resources.
From the tool's definition Tool description states 'Run Python code in the current environment' which enables arbitrary code execution.
Documented attack patterns abuse exactly the kind of access run_python_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Python Code Runner, and nothing reaches the server without passing your rules. This is the rule we recommend for run_python_code:
{
"version": "1",
"default": "deny",
"tools": {
"run_python_code": {
"limits": [
{
"counter": "run_python_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_python_code 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.
Free to start. No card required.
Run Python code in the current environment. It is categorised as a Execute tool in the Python Code Runner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Python Code Runner MCP server in PolicyLayer and add a rule for run_python_code: 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 Python Code Runner. Nothing to install.
run_python_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_python_code 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.
Set action: deny in the PolicyLayer policy for run_python_code. 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.
run_python_code is provided by the Python Code Runner MCP server (shibing624/mcp-run-python-code). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Python Code Runner, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Python Code Runner tools catalogued and risk-classified — across an index of 43,000+ MCP servers.