This record as markdown: /tools/hybridlabor-api-aos/boolean-intersection.md
What boolean_intersection does on Aos
AI agents invoke boolean_intersection 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 boolean_intersection is rated High
Boolean intersection is a geometric computation that modifies the scene by consuming input objects and producing a new intersected solid. This is a non-trivial operation with external side effects in Rhino (objects may be deleted/replaced), classifying it as Execute.
From the tool's definition 'Compute the Boolean intersection of two or more closed breps' — performs a geometric boolean operation that transforms/consumes input geometry and produces new output geometry in Rhino
Attacks that exploit this kind of access
The rule that runs boolean_intersection 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 boolean_intersection, this is the rule to start with:
boolean_intersection 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 boolean_intersection call is checked against it from then on.
Questions about boolean_intersection
Compute the Boolean intersection of two or more closed breps. 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 boolean_intersection: 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.
boolean_intersection 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 boolean_intersection 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 boolean_intersection. 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.
boolean_intersection 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