Remove a node from a Godot scene
AI agents call remove_node to permanently remove resources in Godot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing nodes from Godot scenes deletes structural elements that cannot be restored by the tool itself. While Godot editors typically have undo functionality, the tool description makes no mention of reversibility. In the context of an AI agent autonomously modifying game projects, this action is destructive because it permanently alters the scene structure unless manually undone by a user.
From the tool's definition Tool name 'remove_node' with description 'Remove a node from a Godot scene' indicates deletion of scene components. Removal of nodes from scenes is irreversible without undo/restore capabilities explicitly mentioned.
Attacks that exploit this kind of access
Remove a node from a Godot scene. It is categorised as a Destructive tool in the Godot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot MCP Server 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 Server. Nothing to install.
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 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 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.
remove_node is provided by the Godot MCP Server MCP server (koltyakov/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →