This record as markdown: /tools/caravanglory-cocos-mcp-server/move-array-element.md
What move_array_element does on Cocos
AI agents use move_array_element 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 move_array_element is rated Medium
This action creates or modifies data reversibly—array reordering is non-destructive and can be undone via the undo system (evidenced by begin_undo_recording and cancel_undo_recording tools on the same server). It does not delete data, execute arbitrary code, or trigger financial transactions.
From the tool's definition The tool name and description indicate it moves array element position. Within Cocos Creator editor context, this modifies data structures (array ordering) reversibly without permanent deletion.
Attacks that exploit this kind of access
The rule that runs move_array_element 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_array_element, this is the rule to start with:
move_array_element 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 move_array_element call is checked against it from then on.
Questions about move_array_element
Move array element position. 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 move_array_element: 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.
move_array_element 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 move_array_element 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 move_array_element. 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.
move_array_element 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