This record as markdown: /tools/agentics-ai-code-mcp/run-python.md
What run_python does on Code MCP Server
AI agents invoke run_python to trigger actions in Code MCP Server. 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 run_python is rated High
This tool allows execution of arbitrary Python code within the VS Code workspace environment. While Python execution itself is not inherently destructive, the blast radius is significant because: (1) the tool can read/write files, access environment variables, make network calls, and invoke system commands depending on the Python code executed; (2) an AI agent could be tricked into running malicious or unintended…
From the tool's definition Tool name 'run_python' combined with description 'Execute Python code or script' directly indicates execution of arbitrary code. The tool is explicitly designed to run Python code whose effects depend entirely on the arguments provided.
Attacks that exploit this kind of access
The rule that runs run_python safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every run_python call is checked against it from then on.
Questions about run_python
Execute Python code or script. It is categorised as a Execute tool in the Code MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code MCP Server 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 Code MCP Server. Nothing to install.
run_python 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 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. 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 is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
Across the catalogue