Get the current Unity Editor state including project information
AI agents call get_editor_state to retrieve information from Unity MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves current editor state and project metadata without creating, modifying, deleting, or executing operations. It has no side effects and poses minimal risk—an AI agent using it can only learn about the current project configuration. No data is altered, no code is executed, and no irreversible actions are taken.
From the tool's definition Tool name is 'get_editor_state' and description states 'Get the current Unity Editor state including project information'. The verb 'Get' and action of retrieving state information without modification indicate a read-only operation.
Documented attack patterns abuse exactly the kind of access get_editor_state gives an agent:
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 get_editor_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_editor_state": {}
}
}get_editor_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current Unity Editor state including project information. It is categorised as a Read tool in the Unity MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Integration MCP server in PolicyLayer and add a rule for get_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 Integration. Nothing to install.
get_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 get_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 get_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.
get_editor_state 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.
Deterministic rules across all 15 Unity MCP Integration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Unity MCP Integration tools catalogued and risk-classified — across an index of 42,500+ MCP servers.