This record as markdown: /tools/easehee-rhino-mcp/rhino-named-view-save.md
What rhino_named_view_save does on Rhino
AI agents use rhino_named_view_save to create or update resources in Rhino, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhino environment.
Why rhino_named_view_save is rated Medium
This tool saves (writes) the current camera position as a named view in Rhino. It creates new data (a named view record) reversibly, with no code execution, deletion, or financial implications. Misuse has minimal blast radius since named views can be overwritten or deleted.
From the tool's definition 'Save the current camera as a named view' — creates/stores a new named view entry
Attacks that exploit this kind of access
The rule that runs rhino_named_view_save 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_named_view_save, this is the rule to start with:
rhino_named_view_save stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_named_view_save call is checked against it from then on.
Questions about rhino_named_view_save
Save the current camera as a named view. It is categorised as a Write tool in the Rhino MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_named_view_save: 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_named_view_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rhino_named_view_save 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_named_view_save. 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_named_view_save 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.
This server
Across the catalogue