This record as markdown: /tools/hybridlabor-api-aos/deselect-all.md
What deselect_all does on Aos
AI agents invoke deselect_all 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 deselect_all is rated High
This tool triggers an action in an external application (Rhino), modifying the selection state of the viewport. While it has no persistent data effects, it is an external operation that changes UI/application state rather than merely reading data. It falls under Execute as it drives a Rhino viewport action. Severity is low since deselecting objects has minimal blast radius.
From the tool's definition Deselect all objects in the Rhino viewport
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs deselect_all 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 deselect_all, this is the rule to start with:
deselect_all 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 deselect_all call is checked against it from then on.
Questions about deselect_all
Deselect all objects in the Rhino viewport. 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 deselect_all: 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.
deselect_all 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 deselect_all 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 deselect_all. 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.
deselect_all 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