editor_delete_node

THE RISK

Critical Risk

This tool permanently removes nodes from a Godot scene structure. While Godot's UndoRedo system allows undo operations, the tool's core function is destructive data removal. An AI agent given this tool could accidentally delete critical scene components, animations, or complex node hierarchies.

From the tool's definition Tool name contains 'delete' and description states 'Delete a non-root node from the currently open editor scene'. The UndoRedo mechanism provides reversibility in theory, but the primary action is irreversible deletion of scene data.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access editor_delete_node gives an agent:

HOW TO CONTROL EDITOR_DELETE_NODE

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_delete_node:

policy.json

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

editor_delete_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Godot Devtool — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Godot Devtool tools

Destructive clear_debug_output Clear buffered output for the currently running Godot project Destructive delete_node Delete a non-root node from a Godot scene Destructive filesystem_delete Delete a project-local file or directory with explicit confirmation Destructive filesystem_preview_delete Preview a project-local delete operation without deleting files Execute browser_visualizer_start Start a local read-only browser dashboard for Godot editor/runtime bridge status and live- Execute browser_visualizer_stop Stop the local Browser visualizer HTTP dashboard Execute launch_editor Reuse an already connected Godot editor for a project, launch one only when no bridge is c Execute run_project Run the Godot project and capture output

All 101 Godot Devtool tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Godot Devtool → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the editor_delete_node tool do? +

Delete a non-root node from the currently open editor scene through UndoRedo. It is categorised as a Destructive tool in the Godot Devtool 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_node? +

Register the Godot Devtool MCP server in PolicyLayer and add a rule for editor_delete_node: 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 Devtool. Nothing to install.

What risk level is editor_delete_node? +

editor_delete_node 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_node? +

Yes. Add a rate_limit block to the editor_delete_node 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_node completely? +

Set action: deny in the PolicyLayer policy for editor_delete_node. 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_node? +

editor_delete_node is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Godot Devtool tool call.

Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN GODOT DEVTOOL →

Free to start. No card required.

101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT EDITOR_DELETE_NODE ON GODOT DEVTOOL DOES

// THE RISK

// HOW TO CONTROL EDITOR_DELETE_NODE

// EXPLORE