This record as markdown: /tools/caravanglory-cocos-mcp-server/batch-import-assets.md
What batch_import_assets does on Cocos
AI agents use batch_import_assets 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 batch_import_assets is rated Medium
This tool creates or adds assets to a game engine project, which is a reversible write operation. While assets can typically be deleted, the import itself is not destructive. The 'batch' aspect increases the potential blast radius if an AI agent imports many unwanted or malicious assets, hence medium severity.
From the tool's definition Tool name 'batch_import_assets' and description 'Import multiple assets in batch' indicate creation/addition of assets to the Cocos Creator project. The batch operation amplifies the scope of modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_import_assets 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 batch_import_assets, this is the rule to start with:
batch_import_assets 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 batch_import_assets call is checked against it from then on.
Questions about batch_import_assets
Import multiple assets in batch. 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 batch_import_assets: 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.
batch_import_assets 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 batch_import_assets 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 batch_import_assets. 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.
batch_import_assets 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