AI agents call delete_node to permanently remove resources in Godot Devtool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes scene graph nodes, destroying their configuration, child hierarchy, and associated data within the scene file. While scoped to 'non-root' nodes (limiting blast radius), deletion is irreversible and represents a destructive operation.
From the tool's definition Tool name is 'delete_node' and description states 'Delete a non-root node from a Godot scene'. The verb 'delete' is explicit and irreversible—once a node is removed from a scene, the change cannot be automatically undone without external version control or…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access delete_node gives an agent:
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 delete_node:
{
"version": "1",
"default": "deny",
"hide": [
"delete_node"
]
}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.
Free to start. No card required.
Delete a non-root node from a Godot scene. 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.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for 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.
delete_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 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.
Set action: deny in the PolicyLayer policy for 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.
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.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.