rhino_zoom_object
Zoom the active viewport to fit the given object ids exactly.
This record as markdown: /tools/easehee-rhino-mcp/rhino-zoom-object.md
What rhino_zoom_object does on Rhino
AI agents invoke rhino_zoom_object to trigger actions in Rhino. 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 rhino_zoom_object is rated High
This tool triggers an external operation in Rhino (zooming/panning the active viewport), which is a UI/display action rather than a pure data read. It has no destructive or financial impact, but it does cause a side effect in the running application, placing it in Execute. Blast radius is low since it only affects the viewport display.
From the tool's definition 'Zoom the active viewport to fit the given object ids exactly' — triggers a viewport action in Rhino
Attacks that exploit this kind of access
The rule that runs rhino_zoom_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rhino, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino_zoom_object, this is the rule to start with:
rhino_zoom_object 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 Rhino, apply this rule, and every rhino_zoom_object call is checked against it from then on.
Questions about rhino_zoom_object
Zoom the active viewport to fit the given object ids exactly. It is categorised as a Execute tool in the Rhino MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_zoom_object: 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 Rhino. Nothing to install.
rhino_zoom_object 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 rhino_zoom_object 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 rhino_zoom_object. 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.
rhino_zoom_object is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rhino, and thousands of servers like it.
Across the catalogue