Subtract cutter breps from target breps (Boolean difference).
AI agents invoke boolean_difference 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 difference is a geometry operation that modifies 3D objects by subtracting one shape from another. It transforms/overwrites existing geometry in Rhino, making it an Execute-level operation (running a geometric computation with side effects on the model). While it modifies data, it is a standard CAD operation that can typically be undone within the application, so it does not rise to Destructive.
From the tool's definition Subtract cutter breps from target breps (Boolean difference)
Documented attack patterns abuse exactly the kind of access boolean_difference 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_difference:
{
"version": "1",
"default": "deny",
"tools": {
"boolean_difference": {
"limits": [
{
"counter": "boolean_difference_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}boolean_difference 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.
Subtract cutter breps from target breps (Boolean difference). 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_difference: 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_difference 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_difference 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_difference. 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_difference 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.