remove_node

Remove a node from a scene

SERVERGodot MCP SOURCE6ninelives/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/6ninelives-godot-mcp/remove-node.md

WHAT IT DOES

What remove_node does on Godot MCP

AI agents call remove_node to permanently remove resources in Godot MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_node is rated Critical

Removing a node from a scene deletes the node and its properties/children permanently (unless the user has not saved). This is an irreversible destructive action that cannot be undone programmatically by the tool itself. While Godot's undo system may allow manual recovery, the tool's action is inherently destructive.

From the tool's definition Tool name is 'remove_node' with description 'Remove a node from a scene'. The verb 'remove' indicates deletion of a scene node, which is irreversible within the Godot editor context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_node safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_node, this is the rule to start with:

remove_node Hidden

remove_node 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": [
    "remove_node"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_node

What does the remove_node tool do? +

Remove a node from a scene. It is categorised as a Destructive tool in the Godot MCP 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 remove_node? +

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

What risk level is remove_node? +

remove_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 remove_node? +

Yes. Add a rate_limit block to the 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.

How do I block remove_node completely? +

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

What MCP server provides remove_node? +

remove_node is provided by the Godot MCP server (6ninelives/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 18 Godot tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →