This record as markdown: /tools/hybridlabor-api-aos/fillet-curves.md
What fillet_curves does on Aos
AI agents use fillet_curves to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why fillet_curves is rated Medium
This tool creates new geometry (a fillet arc) which modifies the design file reversibly. It is a Write operation because it creates/adds data to the model without permanently destroying existing data or executing arbitrary code. Severity is medium because misuse could corrupt a design file, but the operation is reversible (undo available in Rhino) and does not involve code execution, deletion, or financial impact.
From the tool's definition Tool name 'fillet_curves' and description 'Create a fillet arc between two curves' indicates creation of new geometry. The server context shows it operates within Rhino 8 to modify the 3D model by adding geometric elements.
Attacks that exploit this kind of access
The rule that runs fillet_curves 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 fillet_curves, this is the rule to start with:
fillet_curves stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 fillet_curves call is checked against it from then on.
Questions about fillet_curves
Create a fillet arc between two curves. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for fillet_curves: 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.
fillet_curves is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fillet_curves 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 fillet_curves. 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.
fillet_curves 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