Execute an Elasticsearch search query using the full Search API body. Pass the complete request body as you would to POST /<index>/_search. Supports query, aggs, size, from, sort, _source, highlight, track_total_hits, and all other Search API parameters. The index parameter is optional — omit it ...
AI agents call es_search to retrieve information from Elasticsearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from Elasticsearch without creating, modifying, deleting, or executing arbitrary code. It is explicitly described as part of a 'read-only' server. Even though it accepts full Search API bodies, the tool is constrained to search/retrieval operations. The blast radius of misuse is limited to information disclosure, not data manipulation or destruction.
From the tool's definition Tool description states: 'Execute an Elasticsearch search query using the full Search API body' and 'A read-only MCP server for Elasticsearch'.
Attacks that exploit this kind of access
Execute an Elasticsearch search query using the full Search API body. Pass the complete request body as you would to POST /<index>/_search. Supports query, aggs, size, from, sort, _source, highlight, track_total_hits, and all other Search API parameters. The index parameter is optional — omit it to search across all indices. It is categorised as a Read tool in the Elasticsearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Elasticsearch MCP Server MCP server in PolicyLayer and add a rule for es_search: 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 MCP Server. Nothing to install.
es_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the es_search 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 es_search. 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.
es_search is provided by the Elasticsearch MCP Server MCP server (maestra-io/mcp-elasticsearch). 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 →