Execute any python within the Unreal Editor. All python must have
AI agents invoke editor_run_python to trigger actions in Unreal. 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 allows execution of arbitrary Python code within the Unreal Editor, giving an AI agent the ability to run any script, modify engine state, invoke editor commands, and perform complex operations. The unconstrained nature ('any python') and the context of running within Unreal Editor—which has deep access to project assets, scene manipulation, and external system calls—makes this critically severe.
From the tool's definition Tool is named 'editor_run_python' and the description explicitly states 'Execute any python within the Unreal Editor.' This enables arbitrary code execution in a powerful game engine environment.
Documented attack patterns abuse exactly the kind of access editor_run_python gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_run_python:
{
"version": "1",
"default": "deny",
"tools": {
"editor_run_python": {
"limits": [
{
"counter": "editor_run_python_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} editor_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.
Free to start. No card required.
Execute any python within the Unreal Editor. All python must have. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unreal MCP server in PolicyLayer and add a rule for editor_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 Unreal. Nothing to install.
editor_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 editor_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 editor_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.
editor_run_python is provided by the Unreal MCP server (runreal/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.