AI agents invoke boolean_union to trigger actions in GOLEM-3DMCP-Rhino-. 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.
Boolean union combines/merges 3D geometry objects in Rhino. This is a geometry modification operation that executes a destructive-ish transformation on existing objects, but is generally reversible via undo in the application. Given the server context of programmatic Rhino control and sibling boolean tools, this falls under Execute as it triggers an external operation (geometry computation) in Rhino.
From the tool's definition Tool name 'boolean_union' on a server that 'create geometry, run booleans, drive Grasshopper... execute arbitrary Python scripts'; sibling tools include boolean_difference and boolean_intersection indicating boolean operations on geometry.
Documented attack patterns abuse exactly the kind of access boolean_union gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GOLEM-3DMCP-Rhino-, and nothing reaches the server without passing your rules. This is the rule we recommend for boolean_union:
{
"version": "1",
"default": "deny",
"tools": {
"boolean_union": {
"limits": [
{
"counter": "boolean_union_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}boolean_union 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.
Free to start. No card required.
boolean_union. It is categorised as a Execute tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for boolean_union: 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 GOLEM-3DMCP-Rhino-. Nothing to install.
boolean_union 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_union 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_union. 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_union is provided by the GOLEM-3DMCP-Rhino- MCP server (thekinghippopotamus/golem-3dmcp-rhino-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GOLEM-3DMCP-Rhino-, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 GOLEM-3DMCP-Rhino- tools catalogued and risk-classified — across an index of 43,000+ MCP servers.