This record as markdown: /tools/caravanglory-cocos-mcp-server/focus-camera-on-nodes.md
What focus_camera_on_nodes does on Cocos
AI agents invoke focus_camera_on_nodes 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 focus_camera_on_nodes is rated High
This tool triggers an editor viewport action (moving/focusing the camera view) in the Cocos Creator editor. It executes an operation that changes the editor's view state rather than reading data or modifying scene assets. It is reversible and has minimal blast radius, but it does perform an active operation in the editor environment.
From the tool's definition Focus scene camera on nodes
Attacks that exploit this kind of access
The rule that runs focus_camera_on_nodes 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 focus_camera_on_nodes, this is the rule to start with:
focus_camera_on_nodes 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 focus_camera_on_nodes call is checked against it from then on.
Questions about focus_camera_on_nodes
Focus scene camera on nodes. 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 focus_camera_on_nodes: 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.
focus_camera_on_nodes 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 focus_camera_on_nodes 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 focus_camera_on_nodes. 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.
focus_camera_on_nodes 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