Permanently delete an agent and all associated runs. Returns: Success message (the API responds 204 No Content on success). Common errors: - 404: Agent not found
AI agents call delete_agent to permanently remove resources in Mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The agent name to delete |
app_id | string | Yes | The app ID |
Parameters from the server's own tool schema.
This tool irreversibly removes an agent and its complete history of runs. Permanent deletion is the defining characteristic of the Destructive category. While the blast radius is somewhat scoped to a single agent entity, the loss of all associated execution history and the inability to recover the agent post-deletion justifies high severity.
From the tool's definition Tool description states 'Permanently delete an agent and all associated runs' — the verb 'permanently delete' combined with 'all associated runs' indicates irreversible data destruction that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_agent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_agent:
{
"version": "1",
"default": "deny",
"hide": [
"delete_agent"
]
}delete_agent disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete an agent and all associated runs. Returns: Success message (the API responds 204 No Content on success). Common errors: - 404: Agent not found. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_agent accepts 2 parameters: name, app_id. Required: name, app_id. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Mcp. 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 MCP server (@butterbase/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
43 Mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.