delete_by_query

Delete documents in an Elasticsearch index based on a query

Server Octodet Elasticsearch octodet/elasticsearch-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_by_query does on Octodet Elasticsearch

AI agents call delete_by_query 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.

Why delete_by_query needs a policy

This tool is categorized as Destructive because it irreversibly deletes data in bulk based on query results. While the deletion is query-based (narrower scope than delete_all), it removes potentially many documents that cannot be restored without backups. The blast radius is high if an agent misuses the query criteria and deletes unintended records.

From the tool's definition delete_by_query performs bulk deletion operations based on matching query criteria. The description explicitly states 'Delete documents in an Elasticsearch index based on a query', indicating irreversible removal of potentially large volumes of data.

Questions about delete_by_query

What does the delete_by_query tool do? +

Delete documents in an Elasticsearch index based on a query. 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.

How do I enforce a policy on delete_by_query? +

Register the Octodet Elasticsearch MCP server in PolicyLayer and add a rule for delete_by_query: 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.

What risk level is delete_by_query? +

delete_by_query is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_by_query? +

Yes. Add a rate_limit block to the delete_by_query 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.

How do I block delete_by_query completely? +

Set action: deny in the PolicyLayer policy for delete_by_query. 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.

What MCP server provides delete_by_query? +

delete_by_query 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.