Delete a document from a specific Elasticsearch index
AI agents call delete_document to permanently remove resources in Octodet Elasticsearch — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from an Elasticsearch index without the ability to reverse the action through the tool itself. Although deletion of individual documents is narrower in blast radius than index-level deletion (delete_index), it is still destructive as it irreversibly removes data.
From the tool's definition Tool name is 'delete_document' with description 'Delete a document from a specific Elasticsearch index'. The verb 'Delete' combined with operation on data documents indicates irreversible removal.
Attacks that exploit this kind of access
Delete a document from a specific Elasticsearch index. It is categorised as a Destructive tool in the Octodet Elasticsearch MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Octodet Elasticsearch 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 Octodet Elasticsearch. 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 Octodet Elasticsearch MCP server (octodet/elasticsearch-mcp). 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 →