AI agents call delete_agent to permanently remove resources in AnythingLLM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an agent without the ability to undo the action. While not as critical as deleting users or workspaces (which could affect multiple entities), deleting an agent is still a destructive operation that irreversibly removes configuration and associated data.
From the tool's definition Tool name is 'delete_agent' with description 'Delete an agent'. The verb 'delete' directly indicates irreversible removal of an agent configuration.
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 AnythingLLM MCP Server, 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.
Delete an agent. It is categorised as a Destructive tool in the AnythingLLM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AnythingLLM MCP Server 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 AnythingLLM MCP Server. 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 AnythingLLM MCP Server MCP server (raqueljezweb/anythingllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AnythingLLM MCP Server, 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.
38 AnythingLLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.