Get Elasticsearch cluster health status, number of nodes, shards, and indices
AI agents call es_cluster_health 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 diagnostic and status information about an Elasticsearch cluster. It performs a GET-style operation to a read-only endpoint, returning cluster metadata without modifying any data or triggering external side effects. The read-only server design and the passive nature of health checks confirm this is a safe Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] Elasticsearch cluster health status, number of nodes, shards, and indices' — a retrieval operation with no side effects. Server is described as 'read-only MCP server'.
Attacks that exploit this kind of access
Get Elasticsearch cluster health status, number of nodes, shards, and 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_cluster_health: 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_cluster_health 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_cluster_health 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_cluster_health. 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_cluster_health 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 →