Delete/unload a collection when done processing. Use after quick_load to clean up temporary data.
AI agents call unload_collection to permanently remove resources in ChromaDB Local 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 a collection and its contents from ChromaDB storage. Although described as 'unload,' the explicit mention of 'Delete' combined with the context of vector database operations means data loss is irreversible. An AI agent misusing this could delete critical indexed knowledge bases or user data without recovery.
From the tool's definition 'Delete/unload a collection' — the description explicitly states deletion of data. Collections in vector databases are irreversible data structures containing embeddings and indexed documents.
Attacks that exploit this kind of access
Delete/unload a collection when done processing. Use after quick_load to clean up temporary data. It is categorised as a Destructive tool in the ChromaDB Local MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ChromaDB Local MCP Server MCP server in PolicyLayer and add a rule for unload_collection: 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 ChromaDB Local MCP Server. Nothing to install.
unload_collection 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 unload_collection 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 unload_collection. 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.
unload_collection is provided by the ChromaDB Local MCP Server MCP server (vespo92/chromadblocal-mcp-server). 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 →