This record as markdown: /tools/caravanglory-cocos-mcp-server/batch-delete-assets.md
What batch_delete_assets does on Cocos
AI agents call batch_delete_assets to permanently remove resources in Cocos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why batch_delete_assets is rated Critical
This tool permanently removes assets without reversible recovery options. In a game development context (Cocos Creator 3.8.x), deleting assets is irreversible and can result in loss of artwork, audio, scripts, and other project resources. Batch deletion magnifies the blast radius. This clearly falls under Destructive rather than Write or Execute, as the operation cannot be undone programmatically.
From the tool's definition Tool name 'batch_delete_assets' and description 'Delete multiple assets in batch' explicitly indicates irreversible deletion of assets. The batch operation amplifies the destructive nature by enabling bulk removal.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_delete_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_delete_assets, this is the rule to start with:
batch_delete_assets is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every batch_delete_assets call is checked against it from then on.
Questions about batch_delete_assets
Delete multiple assets in batch. It is categorised as a Destructive tool in the Cocos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cocos MCP server in PolicyLayer and add a rule for batch_delete_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_delete_assets is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the batch_delete_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_delete_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_delete_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.
Across the catalogue