update_document · ChromaDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_document does on ChromaDB MCP Server

AI agents use update_document 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 update_document needs a policy

This tool modifies data within ChromaDB collections by updating document content. While the operation is reversible and does not permanently delete data, it does alter stored information and could cause issues if an AI agent updates documents with incorrect or malicious content. The medium severity reflects potential data integrity concerns without the irreversibility of destructive operations.

From the tool's definition Tool name 'update_document' and description 'Update a document in a collection' indicate modification of existing data in the vector database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_document Rate-limited

update_document 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": {
    "update_document": {
      "limits": [
        {
          "counter": "update_document_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 update_document

What does the update_document tool do? +

Update a document in 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 update_document? +

Register the ChromaDB MCP Server MCP server in PolicyLayer and add a rule for update_document: 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 update_document? +

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

Can I rate-limit update_document? +

Yes. Add a rate_limit block to the update_document 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 update_document completely? +

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

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