AI agents call wazuh_rules_coverage_map 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.
The tool name 'rules_coverage_map' most likely retrieves or displays rule coverage information—a read operation typical of security analytics and reporting. The '_map' suffix and '_get_' pattern of sibling tools suggest data retrieval with no side effects. No evidence suggests code execution, data modification, deletion, or financial transactions.
From the tool's definition Tool name 'wazuh_rules_coverage_map' suggests retrieval of rule coverage metrics or mapping information. Description is empty, limiting direct evidence, but the sibling tool pattern (alert_summary, compliance_report, cluster_node_stats, get_agent, get_alert,…
Attacks that exploit this kind of access
wazuh_rules_coverage_map. 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_rules_coverage_map: 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_rules_coverage_map 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_rules_coverage_map 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_rules_coverage_map. 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_rules_coverage_map 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 →