delete_node

Delete a node from scene

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

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/caravanglory-cocos-mcp-server/delete-node.md

WHAT IT DOES

What delete_node does on Cocos

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

RISK

Why delete_node is rated Critical

Deletion of scene nodes in a game editor is a destructive action that permanently removes data from the project state. While the Cocos editor may support undo (as suggested by sibling tools like 'begin_undo_recording'), the primary function of this tool is to irreversibly remove scene content.

From the tool's definition Tool name is 'delete_node' and description states 'Delete a node from scene' — this is an irreversible deletion operation that removes scene objects and cannot be undone without explicit undo/redo

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_node safely

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

delete_node Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_node

What does the delete_node tool do? +

Delete a node from scene. It is categorised as a Destructive tool in the Cocos 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 delete_node? +

Register the Cocos 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 Cocos. Nothing to install.

What risk level is delete_node? +

delete_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 delete_node? +

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.

How do I block delete_node completely? +

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.

What MCP server provides delete_node? +

delete_node is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos 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 →