# get_database

Get a Firestore database.

Agent View of the PolicyLayer registry record for `get_database`. HTML page: https://policylayer.com/tools/com-googleapis-firestore-mcp/get-database

## Facts

- Tool: `get_database`
- Server: Mcp (`https://firestore.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-firestore-mcp.md
- Homepage: https://github.com/https://firestore.googleapis.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

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

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_database",
    "arguments": {
      "name": "<name>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_database": {}
  }
}
```

## Other tools on Mcp (22)

- `delete_backup` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-backup.md
- `delete_backup_schedule` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-backup-schedule.md
- `delete_database` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-database.md
- `delete_document` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-document.md
- `delete_index` — Destructive — https://policylayer.com/tools/com-googleapis-firestore-mcp/delete-index.md
- `get_backup` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-backup.md
- `get_backup_schedule` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-backup-schedule.md
- `get_document` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-document.md
- `get_index` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/get-index.md
- `list_backup_schedules` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-backup-schedules.md
- `list_backups` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-backups.md
- `list_collections` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-collections.md
- `list_databases` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-databases.md
- `list_documents` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-documents.md
- `list_indexes` — Read — https://policylayer.com/tools/com-googleapis-firestore-mcp/list-indexes.md
- `add_document` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/add-document.md
- `create_backup_schedule` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-backup-schedule.md
- `create_database` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-database.md
- `create_index` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/create-index.md
- `update_backup_schedule` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-backup-schedule.md
- `update_database` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-database.md
- `update_document` — Write — https://policylayer.com/tools/com-googleapis-firestore-mcp/update-document.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-firestore-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-firestore-mcp