Execute arbitrary C# code in Unity Editor context with full access to UnityEngine and UnityEditor APIs. This is the most powerful tool - it enables you to perform ANY Unity operation without predefined tools. Examples: - Select objects: Selection.activeGameObject = GameObject.Find(
AI agents invoke execute_csharp to trigger actions in Unity 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.
This tool executes arbitrary code (C#) in the Unity Editor environment with unrestricted access to engine and editor APIs. While it could theoretically be used for reads, writes, or destructive operations depending on the code passed to it, the primary capability is code execution with side effects that depend entirely on the AI's input. The 'full access' and 'ANY operation' language indicates no guardrails.
From the tool's definition Execute arbitrary C# code in Unity Editor context with full access to UnityEngine and UnityEditor APIs. The description explicitly states it 'enables you to perform ANY Unity operation' without constraints.
Attacks that exploit this kind of access
Execute arbitrary C# code in Unity Editor context with full access to UnityEngine and UnityEditor APIs. This is the most powerful tool - it enables you to perform ANY Unity operation without predefined tools. Examples: - Select objects: Selection.activeGameObject = GameObject.Find(. It is categorised as a Execute tool in the Unity MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP server in PolicyLayer and add a rule for execute_csharp: 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. Nothing to install.
execute_csharp 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_csharp 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_csharp. 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_csharp is provided by the Unity MCP server (muammar-yacoob/unity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →