# list_documents List documents from a Firestore database. Agent View of the PolicyLayer registry record for `list_documents`. HTML page: https://policylayer.com/tools/com-googleapis-firestore-mcp/list-documents ## Facts - Tool: `list_documents` - Server: Mcp (`https://firestore.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-firestore-mcp.md - Homepage: https://github.com/https://firestore.googleapis.com/mcp - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 11 (1 required) - Recommended policy verdict: Allowed ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `mask` | object | no | Optional. The fields to return. If not set, returns all fields. If a document has a field that is not present in this mask, that field will not be returned in t | | `parent` | string | yes | Required. The parent resource name. In the format: `projects/{project_id}/databases/{database_id}/documents` or `projects/{project_id}/databases/{database_id}/d | | `orderBy` | string | no | Optional. The optional ordering of the documents to return. For example: `priority desc, __name__ desc`. This mirrors the `ORDER BY` used in Firestore queries b | | `pageSize` | integer | no | Optional. The maximum number of documents to return in a single response. Firestore may return fewer than this value. | | `readTime` | string | no | Perform the read at the provided time. This must be a microsecond precision timestamp within the past one hour, or if Point-in-Time Recovery is enabled, can add | | `pageToken` | string | no | Optional. A page token, received from a previous `ListDocuments` response. Provide this to retrieve the subsequent page. When paginating, all other parameters ( | | `recursive` | boolean | no | Optional. If the list should recursively include all documents nested under the parent at any level. If the request specifies a `collection_id`, then the list w | | `showMissing` | boolean | no | If the list should show missing documents. A document is missing if it does not exist, but there are sub-documents nested underneath it. When true, such missing | | `transaction` | string | no | Perform the read as part of an already active transaction. | | `collectionId` | string | no | Optional. The collection ID, relative to `parent`, to list. For example: `chatrooms` or `messages`. This is optional, and when not provided, Firestore will list | | `requestOptions` | object | no | Optional. The request options for this request. | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "list_documents", "arguments": { "parent": "" } } } ``` ## Why list_documents is rated Low Even though list_documents 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. Risk signals: High parameter count (11 properties) ## Use case AI agents call list_documents 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. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp: ```json { "version": "1", "default": "deny", "tools": { "list_documents": {} } } ``` ## Other tools on Mcp (22) - `delete_backup` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-backup.md - `delete_backup_schedule` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-backup-schedule.md - `delete_database` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-database.md - `delete_document` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-document.md - `delete_index` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-index.md - `get_backup` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-backup.md - `get_backup_schedule` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-backup-schedule.md - `get_database` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-database.md - `get_document` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-document.md - `get_index` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-index.md - `list_backup_schedules` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-backup-schedules.md - `list_backups` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-backups.md - `list_collections` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-collections.md - `list_databases` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-databases.md - `list_indexes` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-indexes.md - `add_document` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/add-document.md - `create_backup_schedule` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-backup-schedule.md - `create_database` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-database.md - `create_index` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-index.md - `update_backup_schedule` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-backup-schedule.md - `update_database` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-database.md - `update_document` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-document.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-firestore-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-firestore-mcp