Delete multiple documents from a collection by IDs or filter.
AI agents call batch_delete 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 irreversibly deletes data in bulk from ChromaDB collections. Even though it operates on a local vector database rather than production systems, the Destructive category applies because deletions are permanent and unrecoverable.
From the tool's definition Tool name 'batch_delete' explicitly indicates deletion. Description states 'Delete multiple documents from a collection by IDs or filter' — deletion is irreversible and cannot be undone.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete multiple documents from a collection by IDs or filter. 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 batch_delete: 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.
batch_delete 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 batch_delete 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 batch_delete. 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.
batch_delete 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.
batch_delete is one line of ChromaDB Local MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →