geometry_boolean_union
AI agents invoke geometry_boolean_union to trigger actions in Flex Sensor Agent. 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.
Based on the tool name and server context, this likely performs a boolean union geometry operation within COMSOL, which is an Execute-level action (modifying simulation geometry/model state). The empty description reduces confidence. In COMSOL, boolean union merges geometric objects, which is a model-modification operation that could affect downstream simulation results.
From the tool's definition Tool name 'geometry_boolean_union' on a COMSOL Multiphysics simulation server; description is empty and uninformative.
Attacks that exploit this kind of access
geometry_boolean_union. It is categorised as a Execute tool in the Flex Sensor Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Flex Sensor Agent 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 Flex Sensor Agent. Nothing to install.
geometry_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 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 Flex Sensor Agent MCP server (tonghui666/flex-sensor-agent-mcp). 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 →