Delete currently selected nodes.
AI agents call editor_delete_selected 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.
This tool permanently removes nodes from a Godot project without the ability to undo via the tool itself. Nodes represent fundamental scene graph elements, and their deletion cannot be reversed programmatically by the tool. This is a destructive operation affecting project state.
From the tool's definition Tool name 'editor_delete_selected' combined with description 'Delete currently selected nodes' indicates irreversible deletion of game engine objects.
Attacks that exploit this kind of access
Delete currently selected nodes. 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.
Register the Godot MCP server in PolicyLayer and add a rule for editor_delete_selected: 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_selected 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_selected 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_selected. 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_selected 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.
editor_delete_selected 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 →