Delete a downloaded model from the local node.
AI agents call delete_model to permanently remove resources in Tenzro Ledger MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of data (a model stored on the node). Although the blast radius is somewhat contained to local node state rather than system-wide or financial impact, the destruction of a downloaded model cannot be undone and represents a clear destructive operation.
From the tool's definition The tool name is 'delete_model' and the description states it will 'Delete a downloaded model from the local node.' The verb 'delete' is explicitly destructive, and removing a model is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete a downloaded model from the local node. It is categorised as a Destructive tool in the Tenzro Ledger MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for delete_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 Tenzro Ledger MCP. Nothing to install.
delete_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_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_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_model is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). 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 →