cap_planar_holes
Cap all planar holes in a brep with flat surfaces.
This record as markdown: /tools/hybridlabor-api-aos/cap-planar-holes.md
What cap_planar_holes does on Aos
AI agents use cap_planar_holes 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 cap_planar_holes is rated Medium
This tool modifies existing geometry by adding flat surfaces to close planar holes in a boundary representation (brep). It creates/modifies geometry reversibly within the 3D modeling context, making it a Write operation. Misuse could alter geometry in unintended ways but is not irreversible at the application level.
From the tool's definition Cap all planar holes in a brep with flat surfaces
Attacks that exploit this kind of access
The rule that runs cap_planar_holes 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 cap_planar_holes, this is the rule to start with:
cap_planar_holes 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 cap_planar_holes call is checked against it from then on.
Questions about cap_planar_holes
Cap all planar holes in a brep with flat surfaces. 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 cap_planar_holes: 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.
cap_planar_holes 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 cap_planar_holes 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 cap_planar_holes. 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.
cap_planar_holes 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