This record as markdown: /tools/yanhuifair-godot-mcp/editor-clear-errors.md
What editor_clear_errors does on Godot
AI agents use editor_clear_errors to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
Why editor_clear_errors is rated Medium
Clearing an error list modifies UI/editor state by removing displayed errors, but does not delete files or data. It is reversible in the sense that errors can reappear; however, it does modify (reset) the error list state. This is a Write-level action with low blast radius since it only affects the editor's error display.
From the tool's definition Clear the editor error list
Attacks that exploit this kind of access
The rule that runs editor_clear_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 editor_clear_errors, this is the rule to start with:
editor_clear_errors stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 editor_clear_errors call is checked against it from then on.
Questions about editor_clear_errors
Clear the editor error list. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP server in PolicyLayer and add a rule for editor_clear_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.
editor_clear_errors is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the editor_clear_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 editor_clear_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.
editor_clear_errors 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue