Google Cloud Firestore MCP server
23 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Firestore gives an agent the documents, collections, databases, indexes and backups of the Firestore databases its sign-in reaches. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 23 tools
| Tool | Counted as |
|---|---|
delete_backup | Deletes |
delete_backup_schedule | Deletes |
delete_database | Deletes |
delete_document | Deletes |
delete_index | Deletes |
add_document | Changes things |
create_backup_schedule | Changes things |
create_database | Changes things |
create_index | Changes things |
update_backup_schedule | Changes things |
update_database | Changes things |
update_document | Changes things |
get_backup | Said to only read |
get_backup_schedule | Said to only read |
get_database | Said to only read |
get_document | Said to only read |
get_index | Said to only read |
list_backup_schedules | Said to only read |
list_backups | Said to only read |
list_collections | Said to only read |
list_databases | Said to only read |
list_documents | Said to only read |
list_indexes | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
13 of the last 13 checks passed
A check passes when the server lists its tools. Checked at https://firestore.googleapis.com/mcp.
Recent changes
No change seen across the last 13 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Cloud Firestore's tools change.
One email when Google Cloud Firestore's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its tools can add, update and delete documents, create, update and delete whole databases and backup schedules, and create and delete indexes. Google's Firestore MCP reference
- Its one listed OAuth scope, cloud-platform, lets a sign-in see, edit, configure and delete Google Cloud data. Google's Firestore MCP documentation
- Documents written by other people and apps come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Google Cloud Firestore's own settings, as its documentation describes them. Stackduke has not tested them.
- Google recommends a separate identity for agents that use MCP tools, so that their access can be controlled and monitored. Google's Firestore MCP documentation
- IAM allow and deny policies can allow or refuse tool calls by principal, by service or tool name, by the application's OAuth client, or by whether a tool is marked read-only. Google's Firestore MCP documentation
- Model Armor can screen MCP requests and responses, which Google says helps with risks such as prompt injection and tool poisoning. Google Cloud's MCP servers overview
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.