remove_component

Remove a component from a node. componentType must be the component\

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/remove-component.md

WHAT IT DOES

What remove_component does on Cocos

AI agents call remove_component 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 remove_component is rated Critical

This tool irreversibly deletes a component from a scene node in the Cocos Creator editor. While the editor may support undo/redo, the tool's core function is destructive deletion. In the severity hierarchy, Destructive supersedes Execute and Write.

From the tool's definition The tool 'remove_component' removes a component from a node, which is an irreversible deletion operation that cannot be undone (despite the server offering undo/redo recording, removal is the primary destructive action).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_component 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 remove_component, this is the rule to start with:

remove_component Hidden

remove_component 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_component"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_component

What does the remove_component tool do? +

Remove a component from a node. componentType must be the component\. 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 remove_component? +

Register the Cocos MCP server in PolicyLayer and add a rule for remove_component: 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 remove_component? +

remove_component 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_component? +

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

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

remove_component 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

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 →