clear_game_logs
Delete rotated Godot log backups (optionally the current log too).
This record as markdown: /tools/yanhuifair-godot-mcp/clear-game-logs.md
What clear_game_logs does on Godot
AI agents call clear_game_logs 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
include_current | object | — | Also delete the current godot.log, not just rotated backups. |
Parameters from the server's own tool schema.
Why clear_game_logs is rated Critical
Irreversibly deletes log files; cannot be undone without external recovery.
From the tool's definition Delete rotated Godot log backups, optionally current log.
Attacks that exploit this kind of access
The rule that runs clear_game_logs 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_game_logs, this is the rule to start with:
clear_game_logs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every clear_game_logs call is checked against it from then on.
Questions about clear_game_logs
Delete rotated Godot log backups (optionally the current log too). 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.
clear_game_logs accepts 1 parameter: include_current. 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 clear_game_logs: 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.
clear_game_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_game_logs 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 clear_game_logs. 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.
clear_game_logs 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.
Across the catalogue