This record as markdown: /tools/keeveeg-godot-mcp/delete-save-file.md
What delete_save_file does on Godot
AI agents call delete_save_file 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 |
|---|---|---|---|
slot | integer | Yes | Save slot number to delete (0-99) |
Parameters from the server's own tool schema.
Why delete_save_file is rated Critical
This tool permanently removes user save files, which cannot be undone. Misuse by an AI agent could result in loss of player progress and game state. While not as severe as a system-wide wipe, the irreversibility and user impact justify 'high' severity. Confidence is high due to explicit 'delete' language and unambiguous destructive intent.
From the tool's definition Tool name is 'delete_save_file' and description states 'Delete a save file from a specific slot'. The verb 'delete' combined with irreversible removal of saved game data clearly indicates a destructive operation.
Attacks that exploit this kind of access
The rule that runs delete_save_file 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 delete_save_file, this is the rule to start with:
delete_save_file 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 delete_save_file call is checked against it from then on.
Questions about delete_save_file
Delete a save file from a specific slot. 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.
delete_save_file accepts 1 parameter: slot. Required: slot. 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 delete_save_file: 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.
delete_save_file 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 delete_save_file 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 delete_save_file. 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.
delete_save_file 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.
Across the catalogue