This record as markdown: /tools/caravanglory-cocos-mcp-server/open-scene.md
What open_scene does on Cocos
AI agents use open_scene 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 open_scene is rated Medium
Opening a scene changes the active scene in the editor—a state modification that affects subsequent operations and the editor's in-memory state. This is reversible (you can open a different scene), distinguishing it from Destructive actions. It's more impactful than a Read (which would be querying scene metadata) since it actively modifies editor state.
From the tool's definition Tool name 'open_scene' and description 'Open a scene by path' indicate this loads/switches a scene in the Cocos Creator editor.
Attacks that exploit this kind of access
The rule that runs open_scene 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 open_scene, this is the rule to start with:
open_scene 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 open_scene call is checked against it from then on.
Questions about open_scene
Open a scene by path. 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 open_scene: 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.
open_scene 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 open_scene 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 open_scene. 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.
open_scene 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