This record as markdown: /tools/kiln/add-mesh-chamfer.md
What add_mesh_chamfer does on Kiln
AI agents use add_mesh_chamfer to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why add_mesh_chamfer is rated Medium
This tool modifies 3D model geometry (creates a chamfer on mesh edges), which is a reversible Write operation. While the description is empty (lowering confidence slightly), the name and context strongly suggest mesh design modification rather than execution or destruction.
From the tool's definition Tool name 'add_mesh_chamfer' indicates a modification operation on 3D mesh geometry. The 'add_' prefix and sibling tools like 'add_spool', 'add_assembly_part', and 'add_mesh_fillet' all perform reversible modifications to design data.
Attacks that exploit this kind of access
The rule that runs add_mesh_chamfer 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 add_mesh_chamfer, this is the rule to start with:
add_mesh_chamfer stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 add_mesh_chamfer call is checked against it from then on.
Questions about add_mesh_chamfer
add_mesh_chamfer is a write tool on the Kiln MCP server. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for add_mesh_chamfer: 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.
add_mesh_chamfer 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 add_mesh_chamfer 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 add_mesh_chamfer. 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.
add_mesh_chamfer 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