get_editor_errors
Validate all GDScripts in the current scene tree and return compilation errors
This record as markdown: /tools/keeveeg-godot-mcp/get-editor-errors.md
What get_editor_errors does on Godot
AI agents call get_editor_errors to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_editor_errors is rated Low
This tool performs validation and returns diagnostic information (compilation errors) from GDScripts in the scene tree. It is a read-only operation that queries the state of the codebase without creating, modifying, or deleting any data. The verb 'return' confirms data retrieval semantics. No code execution, resource modification, or destructive action is performed.
From the tool's definition Tool description states 'return compilation errors' — it retrieves and reports validation results without modifying any data or triggering side effects.
Attacks that exploit this kind of access
The rule that runs get_editor_errors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_editor_errors, this is the rule to start with:
get_editor_errors 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 Godot, apply this rule, and every get_editor_errors call is checked against it from then on.
Questions about get_editor_errors
Validate all GDScripts in the current scene tree and return compilation errors. 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 get_editor_errors: 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.
get_editor_errors 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_errors 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_errors. 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_errors is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue