get_rules
AI agents call get_rules 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 tool name 'get_rules' suggests querying or retrieving Wazuh security rules, which would be a read operation with no side effects. However, confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity. In a security platform like Wazuh, rule data retrieval is generally low risk unless rules contain sensitive detection logic that could be exploited.
From the tool's definition Tool name is 'get_rules' with empty description. Based on sibling tools (get_agent_component_stats, get_agent_daemon_stats, get_agent_hardware, get_active_configuration) which are all retrieval operations, this follows a consistent read-only pattern.
Attacks that exploit this kind of access
get_rules. 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 get_rules: 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.
get_rules 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 get_rules 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 get_rules. 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.
get_rules 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 →