This record as markdown: /tools/hybridlabor-api-aos/zoom-extents.md
What zoom_extents does on Aos
AI agents invoke zoom_extents 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_extents is rated High
This tool drives a viewport/UI operation in Rhino (zooming the camera/view), which is an external application action. It doesn't read/write data or delete anything, but it executes a command that changes the state of the Rhino application's viewport. Severity is low because misuse only affects the view, not any geometry or data.
From the tool's definition 'Zoom to the extents of all objects (or selected objects only)' — triggers a viewport action in Rhino
Attacks that exploit this kind of access
The rule that runs zoom_extents 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_extents, this is the rule to start with:
zoom_extents 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_extents call is checked against it from then on.
Questions about zoom_extents
Zoom to the extents of all objects (or selected objects only). 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_extents: 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_extents 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_extents 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_extents. 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_extents 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