This record as markdown: /tools/caravanglory-cocos-mcp-server/reimport-asset.md
What reimport_asset does on Cocos
AI agents invoke reimport_asset to trigger actions in Cocos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why reimport_asset is rated High
Reimporting an asset triggers an editor operation that re-processes asset files through the import pipeline. This is not a simple read or write; it executes an editor-side operation with side effects (regenerating imported data, updating caches). It is not destructive in the irreversible sense but does trigger external processing, making Execute the best fit.
From the tool's definition Reimport an asset — triggers an external operation (re-importing, i.e., re-processing an asset through the editor's import pipeline)
Attacks that exploit this kind of access
The rule that runs reimport_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 reimport_asset, this is the rule to start with:
reimport_asset stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 reimport_asset call is checked against it from then on.
Questions about reimport_asset
Reimport an asset. It is categorised as a Execute tool in the Cocos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cocos MCP server in PolicyLayer and add a rule for reimport_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.
reimport_asset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reimport_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 reimport_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.
reimport_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.
Across the catalogue