This record as markdown: /tools/com-googleapis-firestore-mcp/delete-document.md
What delete_document does on Mcp
AI agents call delete_document 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 |
|---|---|---|---|
name | string | Yes | Required. The resource name of the Document to delete. In the format: `projects/{project_id}/databases/{database_id}/documents/{document_path}`. |
requestOptions | object | — | Optional. The request options for this request. |
currentDocument | object | — | An optional precondition on the document. The request will fail if this is set and not met by the target document. |
Parameters from the server's own tool schema.
Why delete_document is rated Critical
An AI agent that decides to call delete_document doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_document 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_document, this is the rule to start with:
delete_document 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_document call is checked against it from then on.
Questions about delete_document
Delete a document from 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_document accepts 3 parameters: name, requestOptions, currentDocument. 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_document: 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_document 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_document 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_document. 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_document 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