add_component
Add a component to a specific node. IMPORTANT: You must provide the nodeUuid parameter to specify which node to add the component to.
This record as markdown: /tools/caravanglory-cocos-mcp-server/add-component.md
What add_component does on Cocos
AI agents use add_component to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.
Why add_component is rated Medium
This tool creates or modifies editor state by attaching components to nodes, which is reversible (components can be removed). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'add_component' and description 'Add a component to a specific node' indicate creation/modification of scene structure in the Cocos Creator editor.
Attacks that exploit this kind of access
The rule that runs add_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 add_component, this is the rule to start with:
add_component stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every add_component call is checked against it from then on.
Questions about add_component
Add a component to a specific node. IMPORTANT: You must provide the nodeUuid parameter to specify which node to add the component to. It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cocos MCP server in PolicyLayer and add a rule for add_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.
add_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
More on Cocos, and thousands of servers like it.
This server
Across the catalogue