This record as markdown: /tools/hybridlabor-api-aos/run-rhino-command.md
What run_rhino_command does on Aos
AI agents invoke run_rhino_command 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 run_rhino_command is rated High
Running arbitrary Rhino commands, especially given the server's explicit mention of executing Python scripts, permits the AI agent to trigger external operations with effects entirely dependent on command arguments. This is classic Execute category behavior: code/command execution whose consequences depend on what the agent specifies.
From the tool's definition Tool name 'run_rhino_command' combined with server description stating it 'execute[s] arbitrary Python scripts' and gives 'direct, programmatic control of Rhino 8' through natural language.
Attacks that exploit this kind of access
The rule that runs run_rhino_command 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 run_rhino_command, this is the rule to start with:
run_rhino_command 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 run_rhino_command call is checked against it from then on.
Questions about run_rhino_command
run_rhino_command is a execute tool on the Aos MCP server. 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 run_rhino_command: 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.
run_rhino_command 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 run_rhino_command 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 run_rhino_command. 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.
run_rhino_command 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