This record as markdown: /tools/hybridlabor-api-aos/restore-named-view.md
What restore_named_view does on Aos
AI agents invoke restore_named_view 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 restore_named_view is rated High
Restoring a named view triggers an external operation in Rhino that changes the active viewport state (camera position, angle, zoom, etc.). It is not a pure read (it modifies the application state), not a write of persistent geometry, and not destructive. It executes a viewport/UI action within Rhino, making Execute the most appropriate category. Misuse could disorient the scene view but has limited blast radius.
From the tool's definition Restore a previously saved named view
Attacks that exploit this kind of access
The rule that runs restore_named_view 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 restore_named_view, this is the rule to start with:
restore_named_view 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 restore_named_view call is checked against it from then on.
Questions about restore_named_view
Restore a previously saved named view. 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 restore_named_view: 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.
restore_named_view 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 restore_named_view 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 restore_named_view. 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.
restore_named_view 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