Peek at the first few documents in a collection without querying.
AI agents call peek_collection to retrieve information from ChromaDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a sample of documents from a collection for inspection purposes. It does not create, modify, delete, or execute any code. The operation is non-destructive and has no side effects beyond returning data to the user. It fits squarely within the Read category as it 'retrieves or queries data; no side effects'.
From the tool's definition Tool description states 'Peek at the first few documents in a collection without querying' — this is a retrieval operation that returns data for inspection with no side effects.
Attacks that exploit this kind of access
Peek at the first few documents in a collection without querying. It is categorised as a Read tool in the ChromaDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ChromaDB MCP Server MCP server in PolicyLayer and add a rule for peek_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.
peek_collection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the peek_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.
Set action: deny in the PolicyLayer policy for peek_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.
peek_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →