This record as markdown: /tools/yanhuifair-godot-mcp/editor-delete-asset.md
What editor_delete_asset does on Godot
AI agents call editor_delete_asset 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 |
Parameters from the server's own tool schema.
Why editor_delete_asset is rated Critical
Deletion of assets is inherently destructive and cannot be undone. This operation permanently removes files or folder structures from the Godot project, which could break game builds, lose work, or corrupt project state. An AI agent with access to this tool could catastrophically damage a project by deleting critical assets.
From the tool's definition Tool name is 'editor_delete_asset' and description states 'Delete a file or folder via editor.' The verb 'delete' combined with operating on files/folders indicates irreversible removal of data.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_delete_asset 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 editor_delete_asset, this is the rule to start with:
editor_delete_asset 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 editor_delete_asset call is checked against it from then on.
Questions about editor_delete_asset
Delete a file or folder via editor. 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.
editor_delete_asset 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 editor_delete_asset: 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.
editor_delete_asset 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 editor_delete_asset 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 editor_delete_asset. 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.
editor_delete_asset 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