multi_search_simple
AI agents call multi_search_simple to retrieve information from Wazuh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'multi_search_simple' name indicates querying multiple data sources or logs without modification. Sibling tools are predominantly read operations (get_agent_*, count_documents). No evidence of write, delete, or execute capabilities. Severity is medium rather than low due to potential for information disclosure from security platform data access, but confidence is moderate (0.75) due to the missing description.
From the tool's definition Tool name 'multi_search_simple' combined with server context (Wazuh security analysis platform) and sibling tools (search/query operations like 'build_dsql_query', 'count_documents', 'get_*' methods) strongly suggests data retrieval.
Attacks that exploit this kind of access
multi_search_simple. It is categorised as a Read tool in the Wazuh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP Server MCP server in PolicyLayer and add a rule for multi_search_simple: 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 MCP Server. Nothing to install.
multi_search_simple 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 multi_search_simple 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 multi_search_simple. 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.
multi_search_simple is provided by the Wazuh MCP Server MCP server (rayasatriatama/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 →