// SCAN REPORT

Firestore MCP Server

9 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 1 Jul 2026

3 can modify or destroy data

6 read-only

9 tools total

Community server · catalogue entry verified 01/07/2026

How to control Firestore MCP Server ↓

TOOL MAP

What Firestore MCP Server exposes to your agents

Read (6) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Firestore MCP Server tools

Destructive · High delete_document This tool permanently removes data from the database. Write · Medium create_document The tool creates new documents in a Firestore collection, which is a reversible write operation. Write · High update_document This tool creates or modifies data reversibly, which aligns with the Write category.

3 of Firestore MCP Server's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Firestore MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Firestore MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_document": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_document": {
    "limits": [
      {
        "counter": "create_document_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "count_documents": {
    "limits": [
      {
        "counter": "count_documents_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Firestore MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FIRESTORE →

Instant setup, no code required.

FULL CATALOGUE

All 9 Firestore MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_document Delete a document

WRITE 2 tools

Write create_document Create a new document in a collection Write update_document Update an existing document

READ 6 tools

Read count_documents Count documents in a collection Read get_document Get a single document by path Read list_collections List all top-level collections in Firestore Read list_documents List documents in a collection with optional limit Read list_subcollections List subcollections of a document Read query_documents Query documents with filters

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Firestore MCP Server

Can an AI agent delete data through the Firestore MCP Server MCP server? +

Yes. The Firestore MCP Server server exposes 1 destructive tools including delete_document. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Firestore MCP Server? +

The Firestore MCP Server server has 2 write tools including create_document, update_document. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Firestore MCP Server.

How many tools does the Firestore MCP Server MCP server expose? +

9 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Firestore MCP Server? +

Register the Firestore MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Firestore MCP Server tool call.

Deterministic rules across all 9 Firestore MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FIRESTORE →

Instant setup, no code required.

9 Firestore MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.