windows_event_log_cleared
AI agents call windows_event_log_cleared to retrieve information from Velociraptor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the name suggests this retrieves or queries information about whether Windows event logs have been cleared, which is a forensic investigation operation (reading/detecting state) rather than modifying or destructive action. The Read category is appropriate for forensic artifact inspection.
From the tool's definition Tool name 'windows_event_log_cleared' indicates detection/querying of cleared event logs; description is empty but sibling tools on this forensics server (collect_artifact, collect_file, linux_bash_history) are predominantly Read operations for evidence…
Attacks that exploit this kind of access
windows_event_log_cleared. It is categorised as a Read tool in the Velociraptor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Velociraptor MCP Server MCP server in PolicyLayer and add a rule for windows_event_log_cleared: 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 Velociraptor MCP Server. Nothing to install.
windows_event_log_cleared 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 windows_event_log_cleared 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 windows_event_log_cleared. 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.
windows_event_log_cleared is provided by the Velociraptor MCP Server MCP server (snoe-findley/mcp-velociraptor). 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 →