gcp_firestore_delete_document
Delete a Firestore document
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-firestore-delete-document.md
What gcp_firestore_delete_document does on GCP MCP Server
AI agents call gcp_firestore_delete_document to permanently remove resources in GCP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gcp_firestore_delete_document is rated Critical
This tool permanently removes data from a production database without possibility of recovery (unless backups exist outside the tool's scope). The Destructive category applies to actions that cannot be undone. While not as critical as Financial, the high severity reflects potential data loss impact on business operations or user information.
From the tool's definition Tool name explicitly states 'delete_document' and description confirms 'Delete a Firestore document'. Firestore is a NoSQL database, and document deletion is irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs gcp_firestore_delete_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_firestore_delete_document, this is the rule to start with:
gcp_firestore_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 GCP MCP Server, apply this rule, and every gcp_firestore_delete_document call is checked against it from then on.
Questions about gcp_firestore_delete_document
Delete a Firestore document. It is categorised as a Destructive tool in the GCP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_firestore_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 GCP MCP Server. Nothing to install.
gcp_firestore_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 gcp_firestore_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 gcp_firestore_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.
gcp_firestore_delete_document is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
Across the catalogue