AI agents call wazuh_compliance_report 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.
Based on the tool name and sibling context, this tool appears to retrieve compliance audit data from Wazuh rather than execute commands, modify configuration, or trigger alerts. The 'get' and 'summary' patterns among siblings suggest read-only querying. Without a description, confidence is moderated to 0.7, but the categorical assignment to Read is appropriate for a compliance reporting function in a SIEM context.
From the tool's definition Tool name 'wazuh_compliance_report' follows the read-only pattern of sibling tools (wazuh_alert_summary, wazuh_get_alert, wazuh_get_agent, wazuh_get_group, etc.). The server context indicates querying Wazuh SIEM/XDR for compliance audits and triage.
Attacks that exploit this kind of access
wazuh_compliance_report. 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 wazuh_compliance_report: 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.
wazuh_compliance_report 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 wazuh_compliance_report 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 wazuh_compliance_report. 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.
wazuh_compliance_report is provided by the Wazuh MCP server (sbharadwaj05/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 →