AI agents call delete_document 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.
Deleting a document is a destructive operation that cannot be undone. While the blast radius is limited to a single document rather than an entire workspace or system, the irreversible nature of deletion and potential loss of important workspace content justifies 'high' severity. This is categorized as Destructive rather than Write because the operation destroys data permanently with no reversal capability.
From the tool's definition Tool name 'delete_document' combined with description 'Delete a document from a workspace' explicitly indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_document 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_document:
{
"version": "1",
"default": "deny",
"hide": [
"delete_document"
]
}delete_document 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 a document from a workspace. 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_document: 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_document 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_document 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_document. 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_document 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.