Delete a G-code file from the printer's storage.
AI agents call delete_file to permanently remove resources in Kiln — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes G-code files from printer storage without recovery options. While the blast radius is limited to printer files (not system-critical data), the loss of custom print jobs, designs, or configurations cannot be undone. An AI agent with unconstrained access could delete all stored designs or interrupt ongoing work by removing active job files.
From the tool's definition Tool name is 'delete_file' and description states 'Delete a G-code file from the printer's storage.' The verb 'Delete' combined with 'from storage' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a G-code file from the printer's storage. It is categorised as a Destructive tool in the Kiln MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kiln MCP server in PolicyLayer and add a rule for delete_file: 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.
delete_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_file 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 delete_file. 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.
delete_file 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 →