This record as markdown: /tools/caravanglory-cocos-mcp-server/save-scene-as.md
What save_scene_as does on Cocos
AI agents use save_scene_as 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_scene_as is rated Medium
The tool creates or modifies project files by saving scene data to a new location. While the operation is reversible (files can be deleted or overwritten), it modifies the project structure and state. It does not execute arbitrary code, delete data irreversibly, or move money, so Write is the correct category.
From the tool's definition Tool name 'save_scene_as' and description 'Save scene as new file' indicate creation of a new file with scene data. This is a write operation that creates reversible data artifacts in the project.
Attacks that exploit this kind of access
The rule that runs save_scene_as 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_scene_as, this is the rule to start with:
save_scene_as 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_scene_as call is checked against it from then on.
Questions about save_scene_as
Save scene as new 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 save_scene_as: 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_scene_as 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_scene_as 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_scene_as. 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_scene_as 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