This record as markdown: /tools/com-googleapis-firestore-mcp/delete-database.md
What delete_database does on Mcp
AI agents call delete_database to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
etag | string | — | The current etag of the Database. If an etag is provided and does not match the current etag of the database, deletion will be blocked and a FAILED_PRECONDITION |
name | string | Yes | Required. A name of the form `projects/{project_id}/databases/{database_id}` |
Parameters from the server's own tool schema.
Why delete_database is rated Critical
This tool irreversibly destroys data at scale (entire database). Misuse by an AI agent could result in permanent loss of all data, schemas, and indices in a production database. This is the most severe risk category—Destructive—as it represents data loss that cannot be reversed through normal means.
From the tool's definition delete_database performs irreversible deletion of an entire Firestore database. The verb 'delete' combined with the scope 'database' indicates a destructive action that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_database, this is the rule to start with:
delete_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every delete_database call is checked against it from then on.
Questions about delete_database
Delete a Firestore database. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_database accepts 2 parameters: etag, 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 delete_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.
delete_database is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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