List all documents stored in the Chroma vector database with pagination
AI agents call list_documents to retrieve information from Chroma 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 and queries existing documents from the vector database without creating, modifying, or deleting any data. It is a read-only operation that returns information about stored documents. The pagination feature is typical of list/fetch operations. No side effects or data mutation occurs.
From the tool's definition Tool name is 'list_documents' and description states 'List all documents stored in the Chroma vector database with pagination'. The verb 'list' indicates a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_documents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chroma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_documents:
{
"version": "1",
"default": "deny",
"tools": {
"list_documents": {}
}
}list_documents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all documents stored in the Chroma vector database with pagination. It is categorised as a Read tool in the Chroma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chroma MCP Server MCP server in PolicyLayer and add a rule for list_documents: 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 Chroma MCP Server. Nothing to install.
list_documents 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 list_documents 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 list_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.
list_documents is provided by the Chroma MCP Server MCP server (privetin/chroma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Chroma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Chroma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.