Get Elasticsearch cluster information including version, name, and tagline
AI agents call es_cluster_info 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 queries and returns metadata about an Elasticsearch cluster without any side effects, data modification, code execution, or destructive operations. It is a pure read operation that retrieves system information, making it a Read category risk with low severity.
From the tool's definition Tool description states it retrieves 'cluster information including version, name, and tagline' with no modification capability. Server is explicitly described as 'read-only' and tool name 'es_cluster_info' follows a retrieval pattern.
Attacks that exploit this kind of access
Get Elasticsearch cluster information including version, name, and tagline. 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_info: 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_info 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_info 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_info. 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_info 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 →