This record as markdown: /tools/hybridlabor-api-aos/revolve-curve.md
What revolve_curve does on Aos
AI agents invoke revolve_curve 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 revolve_curve is rated High
The tool name 'revolve_curve' strongly suggests a geometry creation operation in Rhino (revolving a curve around an axis to create a surface/solid), which is a Write/Execute operation. The server context explicitly involves programmatic control of Rhino 8 and executing Python scripts. Since the description is empty, confidence is reduced.
From the tool's definition Tool name 'revolve_curve' on a server that 'create geometry, run booleans, drive Grasshopper, capture viewports, and execute arbitrary Python scripts' — sibling tools include geometry operations like boolean_difference, boolean_union, array_objects_linear
Attacks that exploit this kind of access
The rule that runs revolve_curve 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 revolve_curve, this is the rule to start with:
revolve_curve 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 revolve_curve call is checked against it from then on.
Questions about revolve_curve
revolve_curve 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 revolve_curve: 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.
revolve_curve 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 revolve_curve 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 revolve_curve. 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.
revolve_curve 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