add_documents · ChromaDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_documents does on ChromaDB MCP Server

AI agents use add_documents to create or update resources in ChromaDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ChromaDB MCP Server environment.

WHY IT NEEDS A POLICY

Why add_documents needs a policy

This tool creates new data (documents) in the ChromaDB collection, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because bulk malicious document injection could degrade search quality, consume storage, or introduce poisoned embeddings, but the effects are reversible via delete_documents.

From the tool's definition Tool name 'add_documents' and description 'Add documents to a collection' indicate document insertion/creation into a vector database collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_documents Rate-limited

add_documents stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_documents": {
      "limits": [
        {
          "counter": "add_documents_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ChromaDB MCP Server, so you can run agents against it safely.

FAQ

Questions about add_documents

What does the add_documents tool do? +

Add documents to a collection. It is categorised as a Write tool in the ChromaDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_documents? +

Register the ChromaDB MCP Server MCP server in PolicyLayer and add a rule for add_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.

What risk level is add_documents? +

add_documents is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_documents? +

Yes. Add a rate_limit block to the add_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.

How do I block add_documents completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_documents? +

add_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.