chroma_update_documents

Update existing document content or metadata

Modifies stored documents

Part of the ChromaDB MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@chroma-mcp Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use chroma_update_documents to create or modify resources in ChromaDB. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON CHROMA_UPDATE_DOCUMENTS

Without a policy, an AI agent could call chroma_update_documents repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ChromaDB.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

chromadb.yaml

tools:
  chroma_update_documents:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full ChromaDB policy for all 12 tools.

// DETAILS

Tool Name chroma_update_documents

Category Write

MCP Server ChromaDB MCP Server

Risk Level Medium

// MORE CHROMADB TOOLS

Destructive chroma_delete_collection Destructive chroma_delete_documents Write chroma_add_documents Write chroma_create_collection Write chroma_modify_collection Read chroma_get_collection_count Read chroma_get_collection_info Read chroma_get_documents

View all 12 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like chroma_update_documents have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the chroma_update_documents tool do? +

Update existing document content or metadata. It is categorised as a Write tool in the ChromaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chroma_update_documents? +

Add a rule in your Intercept YAML policy under the tools section for chroma_update_documents. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ChromaDB MCP server.

What risk level is chroma_update_documents? +

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

Can I rate-limit chroma_update_documents? +

Yes. Add a rate_limit block to the chroma_update_documents rule in your Intercept 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 chroma_update_documents completely? +

Set action: deny in the Intercept policy for chroma_update_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 chroma_update_documents? +

chroma_update_documents is provided by the ChromaDB MCP server (@chroma-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

chroma_update_documents

Enforce policies on ChromaDB