Return the timestamp of the last rootcheck scan of an agent.
AI agents call get_rootcheck_last_scan 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 queries and returns a timestamp value from an agent's rootcheck scan history. It is a read-only operation that retrieves existing data with no side effects, no code execution, no data modification, and no irreversible actions. The low severity reflects minimal blast radius—misuse would only expose when a security scan last occurred.
From the tool's definition Tool name 'get_rootcheck_last_scan' and description 'Return the timestamp of the last rootcheck scan of an agent' indicate retrieval of metadata without modification or execution.
Attacks that exploit this kind of access
Return the timestamp of the last rootcheck scan of an agent. 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_rootcheck_last_scan: 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_rootcheck_last_scan 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_rootcheck_last_scan 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_rootcheck_last_scan. 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_rootcheck_last_scan 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 →