This record as markdown: /tools/kiln/boolean-mesh-op.md
What boolean_mesh_op does on Kiln
AI agents invoke boolean_mesh_op to trigger actions in Kiln. 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_mesh_op is rated High
Boolean mesh operations (union, subtract, intersect) are computational operations that modify 3D mesh geometry. Given the context of a 3D printer control server and sibling tools like 'add_mesh_chamfer' and 'add_mesh_fillet', this tool likely executes a destructive geometric transformation on a mesh object.
From the tool's definition Tool name 'boolean_mesh_op' suggests a boolean mesh operation (union, difference, intersection) on 3D geometry; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs boolean_mesh_op safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For boolean_mesh_op, this is the rule to start with:
boolean_mesh_op 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 Kiln, apply this rule, and every boolean_mesh_op call is checked against it from then on.
Questions about boolean_mesh_op
boolean_mesh_op is a execute tool on the Kiln MCP server. It is categorised as a Execute tool in the Kiln MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kiln MCP server in PolicyLayer and add a rule for boolean_mesh_op: 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 Kiln. Nothing to install.
boolean_mesh_op 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_mesh_op 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_mesh_op. 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_mesh_op is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue