get_editor_log
Get entries from the editor log, optionally filtered by type
This record as markdown: /tools/keeveeg-godot-mcp/get-editor-log.md
What get_editor_log does on Godot
AI agents call get_editor_log 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max entries to return (default 50) |
filter | string | — | Filter by message type |
Parameters from the server's own tool schema.
Why get_editor_log is rated Low
This tool retrieves historical log entries from the Godot editor without modifying, deleting, or executing anything. It is a straightforward read operation that queries existing data. The optional filtering is a query parameter, not a mutation. Severity is low because editor logs typically contain non-sensitive diagnostic and runtime information with limited blast radius if exposed.
From the tool's definition Tool name is 'get_editor_log' and description states it 'Get entries from the editor log, optionally filtered by type'. The verb 'Get' and the read-only filtering operation indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_editor_log 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_log, this is the rule to start with:
get_editor_log 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_log call is checked against it from then on.
Questions about get_editor_log
Get entries from the editor log, optionally filtered by type. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_editor_log accepts 2 parameters: limit, filter. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for get_editor_log: 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_log 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_log 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_log. 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_log 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