AI agents call list_vulnerabilities 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 queries and returns vulnerability data from the Wazuh Indexer without creating, modifying, deleting, executing code, or moving money. It is a read-only operation that retrieves security information for analysis purposes. The low severity reflects minimal blast radius even if an agent misuses it—at worst, it exposes what vulnerabilities are already known to the system.
From the tool's definition Tool name 'list_vulnerabilities' and description 'List Wazuh vulnerability inventory from the Wazuh Indexer' indicate a retrieval/query operation with no side effects or data modification.
Attacks that exploit this kind of access
List Wazuh vulnerability inventory from the Wazuh Indexer. 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 list_vulnerabilities: 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.
list_vulnerabilities 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 list_vulnerabilities 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 list_vulnerabilities. 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.
list_vulnerabilities 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 →