geometry_boolean_union
AI agents use geometry_boolean_union to create or update resources in COMSOL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your COMSOL MCP Server environment.
A boolean union operation in a geometry context combines multiple shapes into one, which is a reversible modification of the simulation model's geometry. The description is empty, lowering confidence. Based on naming conventions in COMSOL and sibling tool patterns, this likely writes/modifies geometry data rather than executing simulation or destroying data.
From the tool's definition Tool name 'geometry_boolean_union' combined with sibling tools like 'geometry_add_block', 'geometry_add_circle', 'geometry_add_cylinder' suggests this modifies/combines geometry objects in a COMSOL simulation model.
Attacks that exploit this kind of access
geometry_boolean_union. It is categorised as a Write tool in the COMSOL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the COMSOL MCP Server MCP server in PolicyLayer and add a rule for geometry_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 COMSOL MCP Server. Nothing to install.
geometry_boolean_union 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 geometry_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 geometry_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.
geometry_boolean_union is provided by the COMSOL MCP Server MCP server (zhangyoupeng1996/codex_mcp_comsol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →