Delete an index.
AI agents call delete_index to permanently remove resources in Elasticsearch/OpenSearch MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations cannot be undone and represent the highest-severity data loss risk. An AI agent misusing this tool could irreversibly destroy entire indices containing critical business data, making this critical severity. High confidence due to explicit 'delete' verb and clear destructive intent.
From the tool's definition Tool name is 'delete_index' with description 'Delete an index.' Index deletion is irreversible data destruction in Elasticsearch/OpenSearch; all documents and mappings in the index are permanently removed.
Attacks that exploit this kind of access
Delete an index. It is categorised as a Destructive tool in the Elasticsearch/OpenSearch MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Elasticsearch/OpenSearch MCP Server 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 Elasticsearch/OpenSearch MCP Server. 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 Elasticsearch/OpenSearch MCP Server MCP server (rbedoyag/elasticsearch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →