This record as markdown: /tools/com-googleapis-firestore-mcp/delete-index.md
What delete_index does on Mcp
AI agents call delete_index 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. A name of the form `projects/{project_id}/databases/{database_id}/collectionGroups/{collection_id}/indexes/{index_id}` |
Parameters from the server's own tool schema.
Why delete_index is rated Critical
Deleting an index is an irreversible operation that removes database infrastructure and can significantly impact query performance and application functionality. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While not as critical as deleting actual data, index deletion has substantial blast radius if triggered inappropriately by an AI…
From the tool's definition Tool name contains 'delete_index' and description states 'Delete a Firestore index.' The verb 'delete' combined with the irreversible nature of removing database indexes makes this a destructive action.
Attacks that exploit this kind of access
The rule that runs delete_index 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_index, this is the rule to start with:
delete_index 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_index call is checked against it from then on.
Questions about delete_index
Delete a Firestore index. 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_index 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 delete_index: 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_index 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_index 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_index. 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_index 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