unity_selection_focus_scene_view
Control the Scene View camera: frame a GameObject, set pivot/rotation/zoom, toggle orthographic.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-selection-focus-scene-view.md
What unity_selection_focus_scene_view does on Unity MCP Server
AI agents invoke unity_selection_focus_scene_view to trigger actions in Unity MCP Server. 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 unity_selection_focus_scene_view is rated High
This tool triggers external operations within the Unity Editor — manipulating the Scene View camera state (pivot, rotation, zoom, orthographic mode). It doesn't merely read data; it actively changes the editor's viewport state. While not destructive to assets, it executes editor-side operations that affect the working environment, placing it in Execute.
From the tool's definition Control the Scene View camera: frame a GameObject, set pivot/rotation/zoom, toggle orthographic
Attacks that exploit this kind of access
The rule that runs unity_selection_focus_scene_view safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_selection_focus_scene_view, this is the rule to start with:
unity_selection_focus_scene_view 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 Unity MCP Server, apply this rule, and every unity_selection_focus_scene_view call is checked against it from then on.
Questions about unity_selection_focus_scene_view
Control the Scene View camera: frame a GameObject, set pivot/rotation/zoom, toggle orthographic. It is categorised as a Execute tool in the Unity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_selection_focus_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 Unity MCP Server. Nothing to install.
unity_selection_focus_scene_view 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 unity_selection_focus_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 unity_selection_focus_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.
unity_selection_focus_scene_view is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unity MCP Server, and thousands of servers like it.
Across the catalogue