AI agents call wazuh_vulnerability_heatmap 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 pattern (getting/querying vulnerability metrics for display/analysis) aligns with Read operations typical of a SIEM query server. The empty description limits confidence slightly, but the naming convention and context of a security analysis tool suggest data retrieval rather than side effects.
From the tool's definition Tool name contains 'heatmap' and 'vulnerability', suggesting it retrieves and visualizes vulnerability data rather than modifying or executing actions. The server's purpose is to 'query Wazuh SIEM/XDR' for analysis.
Attacks that exploit this kind of access
wazuh_vulnerability_heatmap. 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_vulnerability_heatmap: 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_vulnerability_heatmap 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_vulnerability_heatmap 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_vulnerability_heatmap. 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_vulnerability_heatmap 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 →