Remove a node from the currently open scene.
AI agents call editor_remove_node 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 | Node path to remove |
Parameters from the server's own tool schema.
Removing a node from a Godot scene is a destructive operation that permanently modifies the scene structure. While Godot's editor typically maintains undo history, the tool itself performs an irreversible deletion of scene data.
From the tool's definition Tool name and description: 'Remove a node from the currently open scene' — this irreversibly deletes scene hierarchy data that cannot be trivially recovered without undo/redo history.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Remove a node from the currently open scene. 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.
editor_remove_node 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 editor_remove_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. Nothing to install.
editor_remove_node 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_remove_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.
Set action: deny in the PolicyLayer policy for editor_remove_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.
editor_remove_node 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_remove_node 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 →