This record as markdown: /tools/caravanglory-cocos-mcp-server/save-asset.md
What save_asset does on Cocos
AI agents use save_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 save_asset is rated Medium
This tool modifies asset data by persisting content changes, making it a Write action. It does not delete or irreversibly destroy data (not Destructive), execute arbitrary code (not Execute), handle finances (not Financial), or read-only retrieve data (not Read).
From the tool's definition Tool name 'save_asset' combined with description 'Save asset content' indicates modification of existing asset data in the Cocos Creator editor. The verb 'save' represents persisting changes to asset files, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs save_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 save_asset, this is the rule to start with:
save_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 save_asset call is checked against it from then on.
Questions about save_asset
Save asset content. 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 save_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.
save_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 save_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 save_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.
save_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