planar_surface
Create a planar surface from a closed planar curve boundary.
This record as markdown: /tools/hybridlabor-api-aos/planar-surface.md
What planar_surface does on Aos
AI agents use planar_surface 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 planar_surface is rated Medium
This tool creates new geometry (a planar surface) in the 3D model, which is a reversible Write operation. While it modifies the model state, the action is not destructive (surfaces can be deleted) and does not execute arbitrary code or cause financial impact.
From the tool's definition Tool description states 'Create a planar surface from a closed planar curve boundary' — the verb 'Create' indicates data creation/modification in the Rhino 3D model.
Attacks that exploit this kind of access
The rule that runs planar_surface 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 planar_surface, this is the rule to start with:
planar_surface 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 planar_surface call is checked against it from then on.
Questions about planar_surface
Create a planar surface from a closed planar curve boundary. 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 planar_surface: 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.
planar_surface 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 planar_surface 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 planar_surface. 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.
planar_surface 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