AI agents call diagnose_wazuh_connection to retrieve information from Wazuh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about configuration and connectivity status. It performs no modifications, deletions, code execution, or financial operations. The explicit mention of not exposing credentials suggests it safely queries status without side effects. This aligns with the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool name 'diagnose_wazuh_connection' and description 'Check Wazuh MCP configuration and connectivity' indicate a diagnostic/query operation. The phrase 'without exposing credentials' reinforces this is a read-only operation that does not modify system state.
Attacks that exploit this kind of access
Check Wazuh MCP configuration and connectivity without exposing credentials. It is categorised as a Read tool in the Wazuh MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP server in PolicyLayer and add a rule for diagnose_wazuh_connection: 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. Nothing to install.
diagnose_wazuh_connection 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 diagnose_wazuh_connection 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 diagnose_wazuh_connection. 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.
diagnose_wazuh_connection is provided by the Wazuh MCP server (solomonneas/wazuh-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 →