Comprehensive Elasticsearch cluster health check.
AI agents call es_cluster_health to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a health monitoring/diagnostic tool that queries Elasticsearch cluster status and returns information. Health checks are non-destructive read operations that gather metrics and status data. While it accesses infrastructure systems, the action is informational only with no side effects, no data modification, and no code execution triggered.
From the tool's definition Tool name 'es_cluster_health' and description 'Comprehensive Elasticsearch cluster health check' indicates a diagnostic query operation that retrieves and reports health status information without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Comprehensive Elasticsearch cluster health check. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus 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 RedisNexus. 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 RedisNexus MCP server (rajkumar-madhu/mcp). 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 →