AI agents use merge_mesh_files 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.
Merging mesh files creates a new or modified 3D model file, which is a reversible write operation. Within the context of 3D printer control (Kiln server), this modifies design data that will be used for printing.
From the tool's definition Tool name 'merge_mesh_files' indicates combining or modifying 3D mesh data files. Description is empty, limiting specificity.
Attacks that exploit this kind of access
merge_mesh_files. 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 merge_mesh_files: 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.
merge_mesh_files 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 merge_mesh_files 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 merge_mesh_files. 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.
merge_mesh_files 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.
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 →