This record as markdown: /tools/caravanglory-cocos-mcp-server/change-view-mode-2d-3d.md
What change_view_mode_2d_3d does on Cocos
AI agents invoke change_view_mode_2d_3d to trigger actions in Cocos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why change_view_mode_2d_3d is rated High
This tool changes the view mode in the Cocos Creator editor between 2D and 3D. It triggers an external operation in the editor (modifying the viewport/display mode), not merely reading data. It doesn't create/modify assets or data reversibly in a meaningful sense, but executes an editor action. The blast radius is low as it only affects the editor's visual display mode.
From the tool's definition Change 2D/3D view mode
Attacks that exploit this kind of access
The rule that runs change_view_mode_2d_3d 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 change_view_mode_2d_3d, this is the rule to start with:
change_view_mode_2d_3d stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 change_view_mode_2d_3d call is checked against it from then on.
Questions about change_view_mode_2d_3d
Change 2D/3D view mode. It is categorised as a Execute tool in the Cocos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cocos MCP server in PolicyLayer and add a rule for change_view_mode_2d_3d: 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.
change_view_mode_2d_3d is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the change_view_mode_2d_3d 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 change_view_mode_2d_3d. 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.
change_view_mode_2d_3d 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