AI agents call is_editor_running to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple state query operation with no side effects. It retrieves information about whether the editor is currently running, which is a read-only operation. The blast radius is minimal—an AI agent cannot misuse this to cause harm, corrupt data, or trigger unwanted actions. Low severity reflects the benign nature of the information retrieved.
From the tool's definition Tool name 'is_editor_running' and description 'Check if Godot editor is running' indicate a status check that queries the state of the Godot editor without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if Godot editor is running. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for is_editor_running: 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 Godot. Nothing to install.
is_editor_running 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 is_editor_running 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 is_editor_running. 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.
is_editor_running is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
is_editor_running is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →