copy_node

Copy node for later paste operation

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/copy-node.md

WHAT IT DOES

What copy_node does on Cocos

AI agents use copy_node 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.

RISK

Why copy_node is rated Medium

The tool creates a duplicate of an editor node, which modifies the editor's state by adding new data. This is reversible (via undo) and does not permanently delete or destroy data, making it a Write operation. Severity is medium because misuse could duplicate many nodes and clutter the scene, but the editor provides undo capabilities and the operation itself doesn't affect external systems or permanent data loss.

From the tool's definition Tool name 'copy_node' and description 'Copy node for later paste operation' indicate data duplication within the editor state. This is a reversible write operation that creates a copy of scene data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

copy_node Rate-limited

copy_node 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_node": {
      "limits": [
        {
          "counter": "copy_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about copy_node

What does the copy_node tool do? +

Copy node for later paste operation. 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.

How do I enforce a policy on copy_node? +

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

copy_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit copy_node? +

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

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

copy_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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →