This record as markdown: /tools/com-googleapis-firestore-mcp/get-database.md
What get_database does on Mcp
AI agents call get_database 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 |
|---|---|---|---|
name | string | Yes | Required. A name of the form `projects/{project_id}/databases/{database_id}` |
Parameters from the server's own tool schema.
Why get_database is rated Low
This tool retrieves information about a Firestore database. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius is minimal as it only exposes existing database metadata. Even if an AI agent misuses this tool, it cannot cause harm beyond potentially exposing configuration information.
From the tool's definition Tool name 'get_database' and description 'Get a Firestore database' indicate retrieval of database metadata or configuration without modification. The verb 'get' is a standard Read operation.
Attacks that exploit this kind of access
The rule that runs get_database 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 get_database, this is the rule to start with:
get_database 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 get_database call is checked against it from then on.
Questions about get_database
Get a Firestore database. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_database accepts 1 parameter: name. Required: name. 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 get_database: 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.
get_database 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 get_database 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 get_database. 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.
get_database 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