AI agents invoke save_to_file_and_run 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.
The tool name strongly implies it writes content to a file and then executes it, combining Write and Execute actions. Given the server's purpose of running Python code and the sibling tools focused on execution, this tool almost certainly saves code to a file and runs it. Per severity rules, Execute outranks Write.
From the tool's definition Tool name 'save_to_file_and_run' combined with server context: 'Enables execution of Python code in a safe environment, including running scripts' and sibling tools 'run_python_code', 'run_python_file'. The tool description is empty, lowering confidence.
Documented attack patterns abuse exactly the kind of access save_to_file_and_run 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 save_to_file_and_run:
{
"version": "1",
"default": "deny",
"tools": {
"save_to_file_and_run": {
"limits": [
{
"counter": "save_to_file_and_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}save_to_file_and_run 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.
save_to_file_and_run. 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 save_to_file_and_run: 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.
save_to_file_and_run 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 save_to_file_and_run 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 save_to_file_and_run. 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.
save_to_file_and_run 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.