list_collections
List all the collection IDs underneath a document.
This record as markdown: /tools/com-googleapis-firestore-mcp/list-collections.md
What list_collections does on Mcp
AI agents call list_collections to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | Yes | Required. The parent document. In the format: `projects/{project_id}/databases/{database_id}/documents/{document_path}`. For example: `projects/my-project/datab |
pageSize | integer | — | The maximum number of results to return. |
readTime | string | — | Reads documents as they were at the given time. This must be a microsecond precision timestamp within the past one hour, or if Point-in-Time Recovery is enabled |
pageToken | string | — | A page token. Must be a value from ListCollectionIdsResponse. |
requestOptions | object | — | Optional. The request options for this request. |
Parameters from the server's own tool schema.
Why list_collections is rated Low
Even though list_collections only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_collections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_collections, this is the rule to start with:
list_collections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_collections call is checked against it from then on.
Questions about list_collections
List all the collection IDs underneath a document. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_collections accepts 5 parameters: parent, pageSize, readTime, pageToken, requestOptions. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for list_collections: 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 Mcp. Nothing to install.
list_collections 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_collections 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_collections. 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_collections is provided by the MCP server (https://firestore.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue