convert_to_nurbs
Convert an extrusion or SubD object to a NURBS brep.
This record as markdown: /tools/hybridlabor-api-aos/convert-to-nurbs.md
What convert_to_nurbs does on Aos
AI agents use convert_to_nurbs 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 convert_to_nurbs is rated Medium
This tool performs a reversible geometric transformation. While it modifies object data (changing from extrusion/SubD to NURBS representation), the operation is not destructive—the original geometric intent is preserved and can be converted back. This qualifies as Write rather than Destructive.
From the tool's definition Tool description states it converts geometry objects to NURBS format, which modifies the representation of existing 3D objects in Rhino.
Attacks that exploit this kind of access
The rule that runs convert_to_nurbs 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 convert_to_nurbs, this is the rule to start with:
convert_to_nurbs 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 convert_to_nurbs call is checked against it from then on.
Questions about convert_to_nurbs
Convert an extrusion or SubD object to a NURBS brep. 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 convert_to_nurbs: 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.
convert_to_nurbs 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 convert_to_nurbs 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 convert_to_nurbs. 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.
convert_to_nurbs 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