List documents in a collection with optional limit
AI agents call list_documents to retrieve information from Firestore 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/queries documents from a Firestore collection without creating, modifying, or deleting data. It has no side effects and poses minimal risk if misused by an AI agent—worst case being excessive data exposure or query costs. It clearly falls under the Read category.
From the tool's definition Tool name 'list_documents' combined with description 'List documents in a collection with optional limit' indicates retrieval of data without modification. The server description confirms 'full CRUD operations' where this tool provides the Read component.
Attacks that exploit this kind of access
List documents in a collection with optional limit. It is categorised as a Read tool in the Firestore MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firestore 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 Firestore 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 Firestore MCP Server MCP server (yudai-uk/firestore-mcp). 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 →