This record as markdown: /tools/easehee-rhino-mcp/rhino-view-set.md
What rhino_view_set does on Rhino
AI agents invoke rhino_view_set 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_view_set is rated High
This tool drives the Rhino application to change the active view, which is an external operation with side effects in the host application. It is not purely reading data, but rather executing a state change in Rhino's viewport. It is reversible (you can switch back), so it does not qualify as Destructive, but it does trigger an external action beyond simple data retrieval or creation.
From the tool's definition 'Activate a saved named view' — triggers an external operation in Rhino (changing the active viewport/camera state)
Attacks that exploit this kind of access
The rule that runs rhino_view_set 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_view_set, this is the rule to start with:
rhino_view_set 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_view_set call is checked against it from then on.
Questions about rhino_view_set
Activate a saved named view. 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_view_set: 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_view_set 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_view_set 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_view_set. 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_view_set 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