This record as markdown: /tools/caravanglory-cocos-mcp-server/import-asset.md
What import_asset does on Cocos
AI agents use import_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 import_asset is rated Medium
Importing assets modifies the project state by adding new resources, making it a Write operation rather than Read. The severity is medium because while asset imports are reversible (assets can be deleted), they could introduce malicious or incorrect assets that affect project builds and runtime behavior.
From the tool's definition Tool name 'import_asset' and description 'Import an asset file' indicate creation/addition of new assets to the Cocos Creator project. The verb 'import' is a write operation that introduces external files into the project structure.
Attacks that exploit this kind of access
The rule that runs import_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 import_asset, this is the rule to start with:
import_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 import_asset call is checked against it from then on.
Questions about import_asset
Import an asset file. 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 import_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.
import_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 import_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 import_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.
import_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