Clear all chat history for a workspace
AI agents call clear_chat_history 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 deletes all chat history records for a workspace without restoration mechanism. It is irreversible data destruction, making it Destructive rather than Write (which implies reversible modifications).
From the tool's definition Tool name explicitly uses 'clear' and description states it will 'Clear all chat history for a workspace' — irreversible deletion of conversational data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_chat_history 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 clear_chat_history:
{
"version": "1",
"default": "deny",
"hide": [
"clear_chat_history"
]
} clear_chat_history 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.
Clear all chat history for 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 clear_chat_history: 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.
clear_chat_history 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 clear_chat_history 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 clear_chat_history. 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.
clear_chat_history 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.