This record as markdown: /tools/com-googleapis-firestore-mcp/list-indexes.md
What list_indexes does on Mcp
AI agents call list_indexes 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 |
|---|---|---|---|
filter | string | — | The filter to apply to list results. |
parent | string | Yes | Required. A parent name of the form `projects/{project_id}/databases/{database_id}/collectionGroups/{collection_id}` |
pageSize | integer | — | The number of results to return. |
pageToken | string | — | A page token, returned from a previous call to FirestoreAdmin.ListIndexes, that may be used to get the next page of results. |
Parameters from the server's own tool schema.
Why list_indexes is rated Low
This tool performs a read-only operation that queries and returns information about Firestore indexes. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent listing indexes could only gather metadata about the database structure, which is informational in nature.
From the tool's definition Tool name 'list_indexes' and description 'List Firestore indexes' indicate a retrieval operation with no modification of data. Listing is a query-only action that retrieves information about existing indexes without side effects.
Attacks that exploit this kind of access
The rule that runs list_indexes 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_indexes, this is the rule to start with:
list_indexes 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_indexes call is checked against it from then on.
Questions about list_indexes
List Firestore indexes. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_indexes accepts 4 parameters: filter, parent, pageSize, pageToken. 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_indexes: 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_indexes 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_indexes 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_indexes. 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_indexes 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