unity_execute_code
Execute arbitrary C# code inside the Unity Editor. The code runs in the editor context with access to all Unity APIs. Useful for one-off operations, queries, and automation. Return values are serialized to JSON.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-execute-code.md
What unity_execute_code does on Unity MCP Server
AI agents invoke unity_execute_code to trigger actions in Unity 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 unity_execute_code is rated High
This tool permits execution of arbitrary code within a running application context with full API access. An AI agent could use this to execute malicious scripts, delete files, modify projects, exfiltrate data, or compromise the development environment. The 'arbitrary' qualifier and unrestricted API access elevate this to critical severity.
From the tool's definition Tool explicitly allows 'Execute arbitrary C# code inside the Unity Editor' with 'access to all Unity APIs'. The description directly indicates code execution capability without restrictions on what that code can do.
Attacks that exploit this kind of access
The rule that runs unity_execute_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_execute_code, this is the rule to start with:
unity_execute_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_execute_code call is checked against it from then on.
Questions about unity_execute_code
Execute arbitrary C# code inside the Unity Editor. The code runs in the editor context with access to all Unity APIs. Useful for one-off operations, queries, and automation. Return values are serialized to JSON. It is categorised as a Execute tool in the Unity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_execute_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 Unity MCP Server. Nothing to install.
unity_execute_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 unity_execute_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 unity_execute_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.
unity_execute_code is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unity MCP Server, and thousands of servers like it.
Across the catalogue