unity_editor_state
Get the current Unity Editor state: play mode, compilation status, active scene, project path.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-editor-state.md
What unity_editor_state does on Unity MCP Server
AI agents call unity_editor_state to retrieve information from Unity MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why unity_editor_state is rated Low
This tool queries and returns the current state of the Unity Editor without modifying, executing, or deleting anything. It is a pure read operation with no side effects. The low severity reflects minimal risk even if misused, as it only exposes system state information that an agent would already need to understand the editor's current condition.
From the tool's definition Tool description explicitly uses 'Get' and retrieves state information: 'play mode, compilation status, active scene, project path.' No modifications, deletions, or executions described.
Attacks that exploit this kind of access
The rule that runs unity_editor_state 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_editor_state, this is the rule to start with:
unity_editor_state is read-only, so it stays allowed. 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_editor_state call is checked against it from then on.
Questions about unity_editor_state
Get the current Unity Editor state: play mode, compilation status, active scene, project path. It is categorised as a Read tool in the Unity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_editor_state: 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_editor_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unity_editor_state 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_editor_state. 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_editor_state 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.
This server
Across the catalogue