Delete a file with .bak backup.
AI agents call delete_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 |
|---|---|---|---|
path | string | Yes | Path to file to delete (relative to project root) |
Parameters from the server's own tool schema.
This tool irreversibly removes files from the filesystem. While a .bak backup may be created, the primary action is deletion, which cannot be undone by the tool itself. In the context of a game engine MCP with 282 tools, an AI agent with uncontrolled access could delete critical game assets, source files, or project configuration.
From the tool's definition Tool name is 'delete_file' and description states 'Delete a file with .bak backup.' The verb 'delete' combined with file deletion semantics is explicitly destructive.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Delete a file with .bak backup. 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_file accepts 1 parameter: path. Required: path. 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_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_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_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_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_file 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.
delete_file is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →