// MCP TOOL REFERENCE

CHROMADB TOOLS

12 tools from the ChromaDB MCP Server, categorised by risk level.

READ TOOLS

chroma_get_collection_count Get the document count in a collection 2/5 chroma_get_collection_info Get detailed information about a collection 2/5 chroma_get_documents Retrieve documents by ID or filter 2/5 chroma_list_collections List all collections with pagination 2/5 chroma_peek_collection View a sample of documents in a collection 2/5 chroma_query_documents Query documents using semantic search 2/5

WRITE TOOLS

chroma_add_documents Add documents with metadata and embeddings 3/5 chroma_create_collection Create a new vector collection 3/5 chroma_modify_collection Update a collection name or metadata 3/5 chroma_update_documents Update existing document content or metadata 3/5

DESTRUCTIVE TOOLS

chroma_delete_collection Delete an entire collection permanently 5/5 chroma_delete_documents Delete specific documents from a collection 4/5

// FAQ

How many tools does the ChromaDB MCP server have? +

The ChromaDB MCP server exposes 12 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on ChromaDB tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the ChromaDB server.

What risk categories do ChromaDB tools fall into? +

ChromaDB tools are categorised as Read (6), Write (4), Destructive (2). Each category has a recommended default policy.

Enforce policies on ChromaDB

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →