Delete/remove/destroy an agent configuration permanently. Use when user wants to delete, remove, or destroy an agent completely.
AI agents call delete_agent to permanently remove resources in Snak — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes agent configurations and cannot be undone. While the blast radius is somewhat contained (affects only a single agent's configuration rather than system-wide data), the permanent nature of the operation and its irreversibility classify it as Destructive.
From the tool's definition Tool description explicitly states: "Delete/remove/destroy an agent configuration permanently." The use of "permanently" combined with "delete/remove/destroy" clearly indicates irreversible data loss.
Attacks that exploit this kind of access
Delete/remove/destroy an agent configuration permanently. Use when user wants to delete, remove, or destroy an agent completely. It is categorised as a Destructive tool in the Snak MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Snak MCP server in PolicyLayer and add a rule for delete_agent: 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 Snak. Nothing to install.
delete_agent 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_agent 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_agent. 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_agent is provided by the Snak MCP server (kasarlabs/snak). 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 →