This record as markdown: /tools/keeveeg-godot-mcp/delete-scene.md
What delete_scene does on Godot
AI agents call delete_scene 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 | Scene file path to delete |
force | boolean | — | Force close and delete if scene is currently open |
Parameters from the server's own tool schema.
Why delete_scene is rated Critical
This tool permanently removes scene files from a Godot project. Scene files are critical project assets, and deletion cannot be undone programmatically. While not directly financial or critical infrastructure, accidental or malicious deletion of scene files would cause significant project damage. The high severity reflects the irreversible nature of file deletion and potential impact on project integrity.
From the tool's definition Tool name: delete_scene. Description: Delete a scene file from the project. The verb 'delete' combined with 'file' indicates irreversible removal of data.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs delete_scene 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_scene, this is the rule to start with:
delete_scene 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_scene call is checked against it from then on.
Questions about delete_scene
Delete a scene file 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_scene accepts 2 parameters: path, force. 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_scene: 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_scene 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_scene 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_scene. 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_scene 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