Return the last 13000 entries of wazuh log file (ossec.log).
AI agents call get_manager_logs 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 historical log data from the Wazuh manager without modifying, deleting, or executing any operations. While the severity is rated medium rather than low due to the sensitive nature of security logs (which may contain authentication tokens, system vulnerabilities, or other operational details that could be exploited if leaked), the core function is pure data retrieval with no side effects.
From the tool's definition Tool description states 'Return the last 13000 entries of wazuh log file (ossec.log)' - a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Return the last 13000 entries of wazuh log file (ossec.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_manager_logs: 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_manager_logs 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_manager_logs 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_manager_logs. 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_manager_logs 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 →