get_security_audit_log
AI agents call get_security_audit_log 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.
This tool retrieves security audit log information from the Wazuh platform without modifying, deleting, or executing operations. Audit log access is a read operation with no side effects. Confidence is slightly reduced (0.85 rather than higher) due to the empty description, but the naming convention and context of sibling tools strongly indicate a read-only retrieval function.
From the tool's definition Tool name 'get_security_audit_log' indicates retrieval of audit log data. The naming pattern matches sibling tools on this server (get_agent_hardware, get_agent_netaddr, get_agent_hotfixes) which are all read/retrieval operations.
Attacks that exploit this kind of access
get_security_audit_log. 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_security_audit_log: 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_security_audit_log 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_security_audit_log 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_security_audit_log. 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_security_audit_log 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 →