execute_editor_command

THE RISK

High Risk

This tool permits arbitrary code execution within the Unity Editor runtime. An AI agent could use this to execute malicious scripts, modify project state, exfiltrate data, or compromise the development environment. The 'full flexibility' and ability to use custom namespaces and multiple classes indicates unrestricted code execution capability.

From the tool's definition Tool executes C# code directly in the Unity Editor with full flexibility including custom namespaces and multiple classes. Described as allowing execution of arbitrary code within the editor environment.

Documented attack patterns abuse exactly the kind of access execute_editor_command gives an agent:

HOW TO CONTROL EXECUTE_EDITOR_COMMAND

PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_editor_command:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_editor_command": {
      "limits": [
        {
          "counter": "execute_editor_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

execute_editor_command 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.

Create a free account and register Unity MCP Integration — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Unity MCP Integration tools

Write edit_file Make precise edits to a text file in the Unity project. Returns a git-style diff showing c Write write_file Create a new file or completely overwrite an existing file in the Unity project. Read directory_tree Get a recursive tree view of files and directories in the Unity project as a JSON structur Read find_assets_by_type Find all Unity assets of a specified type (e.g., Material, Prefab, Scene, Script) in the p Read get_current_scene_info Retrieve information about the current scene in Unity Editor with configurable detail leve Read get_editor_state Get the current Unity Editor state including project information Read get_file_info Retrieve detailed metadata about a file or directory in the Unity project. Read get_game_objects_info Retrieve detailed information about specific GameObjects in the current scene

All 15 Unity MCP Integration tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Unity MCP Integration → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the execute_editor_command tool do? +

Execute C# code directly in the Unity Editor - allows full flexibility including custom namespaces and multiple classes. It is categorised as a Execute tool in the Unity MCP Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_editor_command? +

Register the Unity MCP Integration MCP server in PolicyLayer and add a rule for execute_editor_command: 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 Integration. Nothing to install.

What risk level is execute_editor_command? +

execute_editor_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_editor_command? +

Yes. Add a rate_limit block to the execute_editor_command 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.

How do I block execute_editor_command completely? +

Set action: deny in the PolicyLayer policy for execute_editor_command. 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.

What MCP server provides execute_editor_command? +

execute_editor_command is provided by the Unity MCP Integration MCP server (quazaai/unitymcpintegration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Unity MCP Integration tool call.

Deterministic rules across all 15 Unity MCP Integration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN UNITY MCP INTEGRATION →

Free to start. No card required.

15 Unity MCP Integration tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT EXECUTE_EDITOR_COMMAND ON UNITY MCP INTEGRATION DOES

// THE RISK

// HOW TO CONTROL EXECUTE_EDITOR_COMMAND

// EXPLORE