query_collection · ChromaDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_collection does on ChromaDB MCP Server

AI agents invoke query_collection to trigger actions in ChromaDB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why query_collection needs a policy

Based on the tool name and server context (ChromaDB vector database with semantic search capabilities), this tool likely performs a semantic/vector search query against a collection. Querying/searching is typically a Read operation. However, the empty description lowers confidence, and 'query' operations can sometimes execute more complex operations.

From the tool's definition Tool name 'query_collection' on a ChromaDB vector database server; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_collection Rate-limited

query_collection stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_collection": {
      "limits": [
        {
          "counter": "query_collection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 query_collection

What does the query_collection tool do? +

query_collection. It is categorised as a Execute tool in the ChromaDB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query_collection? +

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

What risk level is query_collection? +

query_collection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query_collection? +

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

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

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