AI agents call get_fim_files 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 displays FIM data from a Wazuh agent. It retrieves information about file changes and monitored items without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal — an attacker could only gain visibility into file integrity logs, not alter systems or data.
From the tool's definition Tool description explicitly states it 'Get[s] File Integrity Monitoring (FIM) results' and 'shows monitored files, registry keys, and detected changes' — purely retrieval and reporting of existing security data with no modification, deletion, or execution…
Attacks that exploit this kind of access
Get File Integrity Monitoring (FIM) results for a Wazuh agent — shows monitored files, registry keys, and detected changes. 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 get_fim_files: 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.
get_fim_files 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_fim_files 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_fim_files. 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_fim_files 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 →