获取 Elasticsearch 集群运行状态统计信息
AI agents call get_cluster_stats 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 cluster state information without any side effects. It is a pure read operation that retrieves metrics and statistics. No data is modified, deleted, or executed. The low severity reflects minimal risk—unauthorized read access to cluster stats could reveal infrastructure information but cannot directly compromise data or services.
From the tool's definition Tool retrieves cluster statistics and health information ('获取 Elasticsearch 集群运行状态统计信息' translates to 'Get Elasticsearch cluster runtime status statistics'). No modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
获取 Elasticsearch 集群运行状态统计信息. 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 get_cluster_stats: 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.
get_cluster_stats 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 get_cluster_stats 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 get_cluster_stats. 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.
get_cluster_stats is provided by the Elasticsearch MCP Server MCP server (macgaf/es_mcp_server). 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 →