delete_resource
Delete a Godot resource file (.tres, .res) from the project
This record as markdown: /tools/keeveeg-godot-mcp/delete-resource.md
What delete_resource does on Godot
AI agents call delete_resource 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 | Resource file path to delete |
Parameters from the server's own tool schema.
Why delete_resource is rated Critical
This tool irreversibly deletes resource files from a Godot project. Deletion cannot be undone within the tool's scope, making it a destructive operation. The high severity reflects that loss of project resources (scenes, assets, scripts) could render a project incomplete or broken. Confidence is high because the description explicitly states deletion of files.
From the tool's definition delete_resource: Delete a Godot resource file (.tres, .res) from the project
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs delete_resource 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_resource, this is the rule to start with:
delete_resource 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_resource call is checked against it from then on.
Questions about delete_resource
Delete a Godot resource file (.tres, .res) from the project. 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_resource 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_resource: 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_resource 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_resource 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_resource. 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_resource 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