This record as markdown: /tools/hybridlabor-api-aos/zoom-selected.md
What zoom_selected does on Aos
AI agents invoke zoom_selected to trigger actions in Aos. 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 zoom_selected is rated High
This tool drives a UI/viewport action in Rhino 8 (zooming the camera to selected objects), which constitutes triggering an external operation in a running application. It does not merely read data but actively changes the state of the viewport. No data is created, modified, or destroyed, but it executes an external application command, placing it in Execute rather than Read.
From the tool's definition 'Zoom to show specific objects in a viewport' — triggers a viewport action in Rhino, an external application operation
Attacks that exploit this kind of access
The rule that runs zoom_selected safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_selected, this is the rule to start with:
zoom_selected 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 Aos, apply this rule, and every zoom_selected call is checked against it from then on.
Questions about zoom_selected
Zoom to show specific objects in a viewport. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for zoom_selected: 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 Aos. Nothing to install.
zoom_selected 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 zoom_selected 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 zoom_selected. 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.
zoom_selected is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue