import_collection · ChromaDB Local MCP Server MCP

WHAT IT DOES

What import_collection does on ChromaDB Local MCP Server

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

WHY IT NEEDS A POLICY

Why import_collection needs a policy

The import operation modifies the vector database state by adding or restoring collection data from an external source. While not destructive (reversible via delete), and not inherently dangerous without financial impact, it is a write operation that could introduce malicious data, corrupt the vector index, or overwrite existing collections depending on import logic.

From the tool's definition Tool performs 'Import a collection from a JSON export file' which creates or modifies data in the ChromaDB vector storage by loading external data. This is a write operation that adds/restores data to the database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_collection Rate-limited

import_collection 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": {
    "import_collection": {
      "limits": [
        {
          "counter": "import_collection_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 Local MCP Server, so you can run agents against it safely.

FAQ

Questions about import_collection

What does the import_collection tool do? +

Import a collection from a JSON export file. It is categorised as a Write tool in the ChromaDB Local 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 import_collection? +

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

What risk level is import_collection? +

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

Can I rate-limit import_collection? +

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

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

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