reset_scene_view
Reset scene view to default settings
This record as markdown: /tools/caravanglory-cocos-mcp-server/reset-scene-view.md
What reset_scene_view does on Cocos
AI agents use reset_scene_view 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 reset_scene_view is rated Medium
Resetting the scene view modifies the editor's viewport/camera settings back to defaults. This is a reversible change to editor state (view settings), not data destruction, code execution, or financial action. It falls under Write as it modifies editor configuration, though with low severity since it only affects the visual viewport and not actual scene or asset data.
From the tool's definition Reset scene view to default settings
Attacks that exploit this kind of access
The rule that runs reset_scene_view 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 reset_scene_view, this is the rule to start with:
reset_scene_view 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 reset_scene_view call is checked against it from then on.
Questions about reset_scene_view
Reset scene view to default settings. 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 reset_scene_view: 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.
reset_scene_view 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 reset_scene_view 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 reset_scene_view. 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.
reset_scene_view 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