New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

editor_get_errors

Get current editor error/log list.

SERVERGodot SOURCE@yanhuifair/godot-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-errors.md

What editor_get_errors does on Godot

AI agents call editor_get_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 editor_get_errors is rated Low

This tool retrieves diagnostic information (errors and logs) from the Godot editor without modifying, executing, or deleting any data. It is purely observational and informational in nature. The blast radius of misuse is minimal—at worst, an AI could spam queries or exhaust resources, but cannot cause harm to projects or game states. Low severity is appropriate for a read-only diagnostic tool.

From the tool's definition Tool name 'editor_get_errors' and description 'Get current editor error/log list' indicate a retrieval operation with no side effects. The verb 'Get' and the passive nature of reading existing error/log data confirm this is a read-only query.

Questions about editor_get_errors

What does the editor_get_errors tool do? +

Get current editor error/log list. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_get_errors? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_get_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.

What risk level is editor_get_errors? +

editor_get_errors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit editor_get_errors? +

Yes. Add a rate_limit block to the editor_get_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.

How do I block editor_get_errors completely? +

Set action: deny in the PolicyLayer policy for editor_get_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.

What MCP server provides editor_get_errors? +

editor_get_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Godot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.