This record as markdown: /tools/kiln/repair-mesh.md
What repair_mesh does on Kiln
AI agents invoke repair_mesh 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 repair_mesh is rated High
In the context of 3D printing software, 'repair_mesh' typically refers to analyzing and modifying a 3D mesh to fix errors (e.g., non-manifold edges, holes). This is most likely a Write or Execute operation that processes and potentially modifies mesh geometry. Given the empty description, confidence is low.
From the tool's definition Tool name 'repair_mesh' on a 3D printer control server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs repair_mesh 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 repair_mesh, this is the rule to start with:
repair_mesh 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 repair_mesh call is checked against it from then on.
Questions about repair_mesh
repair_mesh 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 repair_mesh: 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.
repair_mesh 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 repair_mesh 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 repair_mesh. 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.
repair_mesh 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