editor_delete_selected

Delete currently selected nodes.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-delete-selected.md

WHAT IT DOES

What editor_delete_selected does on Godot

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.

RISK

Why editor_delete_selected is rated Critical

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

RECOMMENDED RULE

The rule that runs editor_delete_selected 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_selected, this is the rule to start with:

editor_delete_selected Hidden

editor_delete_selected is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "editor_delete_selected"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_delete_selected call is checked against it from then on.

FAQ

Questions about editor_delete_selected

What does the editor_delete_selected tool do? +

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.

How do I enforce a policy on editor_delete_selected? +

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.

What risk level is editor_delete_selected? +

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.

Can I rate-limit editor_delete_selected? +

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.

How do I block editor_delete_selected completely? +

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.

What MCP server provides editor_delete_selected? +

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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →