node_delete

A destructive tool on the Godot MCP server.

SERVERGodot SOURCEchanceflow/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/chanceflow-godot-mcp/node-delete.md

WHAT IT DOES

What node_delete does on Godot

AI agents call node_delete 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.

RISK

Why node_delete is rated Critical

Deletion of nodes in a game scene cannot be undone through normal tool operations and represents permanent loss of data/structure within a project. This is more severe than Write (which is reversible) and qualifies as Destructive.

From the tool's definition Tool name 'node_delete' indicates deletion operation. In the context of a Godot game engine interaction server, this deletes scene nodes irreversibly. Description is empty, reducing certainty slightly, but the name and context are clear.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_delete safely

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

node_delete Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about node_delete

What does the node_delete tool do? +

node_delete is a destructive tool on the Godot MCP server. 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.

How do I enforce a policy on node_delete? +

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

What risk level is node_delete? +

node_delete 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 node_delete? +

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

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

node_delete is provided by the Godot MCP server (chanceflow/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 84 Godot tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →