clear_editor_log

Clear the editor output log

SERVERGodot SOURCE@keeveeg/godot-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/clear-editor-log.md

WHAT IT DOES

What clear_editor_log does on Godot

AI agents call clear_editor_log to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_editor_log is rated Critical

Clearing the editor output log destroys existing log data with no way to recover it, making this a destructive action. While the blast radius is limited (only log data is lost, not project files or code), the action is irreversible. Severity is medium because it could hinder debugging by permanently removing diagnostic information.

From the tool's definition 'Clear the editor output log' — clearing log data is irreversible; the log entries are permanently removed

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_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 clear_editor_log, this is the rule to start with:

clear_editor_log Hidden

clear_editor_log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_editor_log"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every clear_editor_log call is checked against it from then on.

FAQ

Questions about clear_editor_log

What does the clear_editor_log tool do? +

Clear the editor output log. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_editor_log? +

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

What risk level is clear_editor_log? +

clear_editor_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_editor_log? +

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

How do I block clear_editor_log completely? +

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

What MCP server provides clear_editor_log? +

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

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →