Get the health status of the OpenSearch cluster.
AI agents call cluster_health to retrieve information from OpenSearch 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 data retrieval operation to monitor cluster health—a standard diagnostic query. It has no capacity to modify, delete, or execute operations. The blast radius of misuse is minimal (information disclosure), making severity low. High confidence due to clear read-only semantics in both name and description.
From the tool's definition Tool name 'cluster_health' and description 'Get the health status of the OpenSearch cluster' indicate a read-only query operation that retrieves cluster state information without modification or side effects.
Attacks that exploit this kind of access
Get the health status of the OpenSearch cluster. It is categorised as a Read tool in the OpenSearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenSearch MCP Server MCP server in PolicyLayer and add a rule for 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 OpenSearch MCP Server. Nothing to install.
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 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 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.
cluster_health is provided by the OpenSearch MCP Server MCP server (suriyakumar-hait/opensearch_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 →