This record as markdown: /tools/caravanglory-cocos-mcp-server/delete-asset.md
What delete_asset does on Cocos
AI agents call delete_asset 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 delete_asset is rated Critical
Deleting assets in a game engine like Cocos Creator is an irreversible operation that destroys data without the ability to undo through normal tool invocation (though the server offers undo recording via separate tools, the delete itself is destructive). The impact is high because asset deletion can cripple a project, remove game resources, and cause significant data loss.
From the tool's definition Tool name is 'delete_asset' with description 'Delete an asset'. The verb 'delete' is explicitly destructive and irreversible. This is further supported by the presence of sibling tool 'batch_delete_assets' in the same server, confirming the destructive intent.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_asset, this is the rule to start with:
delete_asset 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 delete_asset call is checked against it from then on.
Questions about delete_asset
Delete an asset. 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 delete_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.
delete_asset 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 delete_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 delete_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.
delete_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