firestore-get-collection-by-path

Get documents from a collection using full path (supports subcollections)

Part of the Firestore Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents call firestore-get-collection-by-path to retrieve information from Firestore Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON FIRESTORE-GET-COLLECTION-BY-PATH

Even though firestore-get-collection-by-path only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

devlimelabs-firestore-mcp.yaml

tools:
  firestore-get-collection-by-path:
    rules:
      - action: allow

See the full Firestore Server policy for all 23 tools.

// DETAILS

Tool Name firestore-get-collection-by-path

Category Read

MCP Server Firestore Server MCP Server

Risk Level Low

// MORE FIRESTORE SERVER TOOLS

Destructive firestore-array-remove Destructive firestore-delete-document Destructive firestore-delete-document-by-path Destructive firestore-delete-field Execute firestore-field-value-batch Execute firestore-transaction Write firestore-array-union Write firestore-batch-write

View all 23 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like firestore-get-collection-by-path have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the firestore-get-collection-by-path tool do? +

Get documents from a collection using full path (supports subcollections). It is categorised as a Read tool in the Firestore Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on firestore-get-collection-by-path? +

Add a rule in your Intercept YAML policy under the tools section for firestore-get-collection-by-path. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Firestore Server MCP server.

What risk level is firestore-get-collection-by-path? +

firestore-get-collection-by-path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit firestore-get-collection-by-path? +

Yes. Add a rate_limit block to the firestore-get-collection-by-path rule in your Intercept 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.

How do I block firestore-get-collection-by-path completely? +

Set action: deny in the Intercept policy for firestore-get-collection-by-path. 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.

What MCP server provides firestore-get-collection-by-path? +

firestore-get-collection-by-path is provided by the Firestore Server MCP server (devlimelabs/firestore-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

firestore-get-collection-by-path

Enforce policies on Firestore Server