This record as markdown: /tools/caravanglory-cocos-mcp-server/move-asset.md
What move_asset does on Cocos
AI agents use move_asset 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_asset is rated Medium
Moving an asset modifies project state by changing its file path or location, but this operation is typically reversible (can be undone via version control or editor undo). It does not irreversibly delete data, execute arbitrary code, or commit financial obligations.
From the tool's definition Tool name 'move_asset' and description 'Move an asset to another location' indicate a reversible modification operation that changes the location/organization of assets within the Cocos Creator project structure.
Attacks that exploit this kind of access
The rule that runs move_asset 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_asset, this is the rule to start with:
move_asset 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_asset call is checked against it from then on.
Questions about move_asset
Move an asset to another location. 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_asset: 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_asset 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_asset 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_asset. 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_asset 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