clear_output

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-output.md

WHAT IT DOES

What clear_output does on Godot

AI agents call clear_output 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_output is rated Critical

Clearing the output log irreversibly removes existing log data that cannot be recovered. While the blast radius is moderate (only log data is lost, not project assets), the action is non-reversible, placing it in the Destructive category.

From the tool's definition Clear the editor output log

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clear_output Hidden

clear_output 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_output"
  ]
}

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_output call is checked against it from then on.

FAQ

Questions about clear_output

What does the clear_output 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_output? +

Register the Godot MCP server in PolicyLayer and add a rule for clear_output: 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_output? +

clear_output 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_output? +

Yes. Add a rate_limit block to the clear_output 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_output completely? +

Set action: deny in the PolicyLayer policy for clear_output. 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_output? +

clear_output 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 →