list_databases

List Firestore databases.

SERVERMcp SOURCEhttps://firestore.googleapis.com/mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-firestore-mcp/list-databases.md

WHAT IT DOES

What list_databases does on Mcp

AI agents call list_databases 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
`parent`	string	Yes	Required. A parent name of the form `projects/{project_id}`
`showDeleted`	boolean	—	If true, also returns deleted resources.

Parameters from the server's own tool schema.

RISK

Why list_databases is rated Low

This tool queries and lists existing Firestore databases, which is a non-destructive retrieval operation. It has no side effects, cannot modify data, and presents minimal risk if misused by an AI agent—the worst outcome would be information disclosure of database names that likely aren't sensitive. Classified as Read with low severity.

From the tool's definition Tool name 'list_databases' and description 'List Firestore databases' indicate a read-only operation that retrieves information without modifying or deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_databases 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_databases, this is the rule to start with:

list_databases Allowed

list_databases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_databases": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_databases call is checked against it from then on.

FAQ

Questions about list_databases

What does the list_databases tool do? +

List Firestore databases. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does list_databases accept? +

list_databases accepts 2 parameters: parent, showDeleted. Required: parent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_databases? +

Register the MCP server in PolicyLayer and add a rule for list_databases: 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.

What risk level is list_databases? +

list_databases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_databases? +

Yes. Add a rate_limit block to the list_databases 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.

How do I block list_databases completely? +

Set action: deny in the PolicyLayer policy for list_databases. 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 list_databases? +

list_databases 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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 23 tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →