Delete documents from a collection.
AI agents call delete_documents to permanently remove resources in ChromaDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of documents is a destructive, non-reversible operation that permanently removes data from the vector database collection. While the blast radius is scoped to a specific collection (not system-wide), the inability to undo the action and potential loss of indexed documents and embeddings justifies 'high' severity. This is clearly more severe than Write operations but does not involve financial transactions.
From the tool's definition Tool name 'delete_documents' with description 'Delete documents from a collection.' - the verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete documents from a collection. It is categorised as a Destructive tool in the ChromaDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ChromaDB MCP Server MCP server in PolicyLayer and add a rule for delete_documents: 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 MCP Server. Nothing to install.
delete_documents 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_documents 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_documents. 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_documents is provided by the ChromaDB MCP Server MCP server (rkilchmn/chroma-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 →