move_node

Move node to new parent

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/move-node.md

WHAT IT DOES

What move_node does on Cocos

AI agents use move_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 move_node is rated Medium

This tool modifies the scene hierarchy by repositioning a node's parent reference—a reversible Write operation. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or create financial obligations. In a game editor context, moving nodes is a fundamental editing operation.

From the tool's definition Tool name 'move_node' and description 'Move node to new parent' indicate modification of scene hierarchy structure. The action relocates a node within the editor's scene graph, which is a reversible structural change rather than deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

move_node Rate-limited

move_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": {
    "move_node": {
      "limits": [
        {
          "counter": "move_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 move_node call is checked against it from then on.

FAQ

Questions about move_node

What does the move_node tool do? +

Move node to new parent. 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 move_node? +

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

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

Can I rate-limit move_node? +

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

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

move_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

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

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