Get cluster health status
AI agents call get_cluster_health to retrieve information from mcp-OpenSearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves operational status information about an OpenSearch cluster. It performs no data modification, deletion, or external operations—it is a pure read operation with no side effects. The blast radius of misuse is minimal, limited to potential information disclosure about cluster state.
From the tool's definition Tool name 'get_cluster_health' and description 'Get cluster health status' indicate retrieval of cluster metadata without modification or side effects.
Attacks that exploit this kind of access
Get cluster health status. It is categorised as a Read tool in the mcp-OpenSearch MCP Server, which means it retrieves data without modifying state.
Register the mcp-OpenSearch MCP server in PolicyLayer and add a rule for get_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 mcp-OpenSearch. Nothing to install.
get_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 get_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 get_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.
get_cluster_health is provided by the mcp-OpenSearch MCP server (showjason/opensearch-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 →