Remove a model from the local cache (file and metadata).
AI agents call delete_cached_model 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 deletes cached 3D model files and their metadata without recovery option. While the impact is scoped to cached models (not active print jobs or system files), deletion of design files represents irreversible data loss. In a 3D printing workflow context, cached models may include expensive design iterations, custom configurations, or user-generated content.
From the tool's definition Tool name explicitly states 'delete_cached_model' and description confirms 'Remove a model from the local cache (file and metadata)' — irreversible deletion of data.
Attacks that exploit this kind of access
Remove a model from the local cache (file and metadata). 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_cached_model: 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_cached_model 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_cached_model 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_cached_model. 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_cached_model 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 →