get_cluster_healthcheck
AI agents call get_cluster_healthcheck to retrieve information from Wazuh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'healthcheck' purpose strongly suggest this is a data retrieval operation that queries the status of cluster components without side effects. While the description is empty (lowering confidence slightly), the tool name and server context indicate read-only diagnostic functionality typical of system monitoring platforms. No evidence of data modification, execution, deletion, or financial impact.
From the tool's definition Tool name 'get_cluster_healthcheck' indicates retrieval of cluster health status information. No description provided, but naming convention and context within a security monitoring platform (Wazuh) suggests this queries system state rather than modifying it.
Attacks that exploit this kind of access
get_cluster_healthcheck. It is categorised as a Read tool in the Wazuh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP Server MCP server in PolicyLayer and add a rule for get_cluster_healthcheck: 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 Wazuh MCP Server. Nothing to install.
get_cluster_healthcheck 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_healthcheck 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_healthcheck. 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_healthcheck is provided by the Wazuh MCP Server MCP server (rayasatriatama/wazuh-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 →