execute_python
Execute arbitrary Python code inside the running Unreal Editor.
This record as markdown: /tools/aadeshrao123-unreal-mcp/execute-python.md
What execute_python does on Unreal-MCP
AI agents invoke execute_python to trigger actions in Unreal-MCP. 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 execute_python is rated High
This tool allows execution of arbitrary code within the Unreal Editor process, which can modify editor state, create/delete assets, trigger builds, access the file system, and perform other actions whose effects are entirely determined by the Python code supplied.
From the tool's definition Tool name and description: 'Execute arbitrary Python code inside the running Unreal Editor.' The word 'Execute' combined with 'arbitrary' Python code indicates the ability to run unrestricted code with side effects dependent on the arguments provided.
Attacks that exploit this kind of access
The rule that runs execute_python safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_python, this is the rule to start with:
execute_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 Unreal-MCP, apply this rule, and every execute_python call is checked against it from then on.
Questions about execute_python
Execute arbitrary Python code inside the running Unreal Editor. It is categorised as a Execute tool in the Unreal-MCP 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 execute_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-MCP. Nothing to install.
execute_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 execute_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 execute_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.
execute_python is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue