This record as markdown: /tools/hybridlabor-api-aos/set-active-view.md
What set_active_view does on Aos
AI agents invoke set_active_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 set_active_view is rated High
This tool changes the active viewport in Rhino, which is an external application state change. While not destructive or data-modifying in a traditional sense, it triggers an operation in an external tool (Rhino), classifying it as Execute. The blast radius is low since it only affects which viewport is currently active and does not modify geometry or data.
From the tool's definition 'Set the active Rhino viewport by name' — triggers an external operation within Rhino that changes application state
Attacks that exploit this kind of access
The rule that runs set_active_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 set_active_view, this is the rule to start with:
set_active_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 set_active_view call is checked against it from then on.
Questions about set_active_view
Set the active Rhino viewport by name. 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 set_active_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.
set_active_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 set_active_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 set_active_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.
set_active_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