List all Elasticsearch indices with their health, status, document count, and storage size
AI agents call es_index_list 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 performs a query operation that retrieves cluster metadata without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—returning index information does not compromise system integrity or enable downstream attacks without additional tools.
From the tool's definition Tool lists Elasticsearch indices with metadata (health, status, document count, storage size) without modification. Server is explicitly described as 'read-only'.
Attacks that exploit this kind of access
List all Elasticsearch indices with their health, status, document count, and storage size. 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_index_list: 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_index_list 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_index_list 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_index_list. 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_index_list 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 →