windows_event_logs
AI agents call windows_event_logs 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.
Event log collection is a read operation that queries historical system events without side effects or modifications. Severity is medium rather than low because event logs may contain sensitive information (credentials, internal IP addresses, user activities) that could inform further attacks, and the tool operates within an incident response context where misuse could expose forensic evidence or compromise ongoing…
From the tool's definition Tool name 'windows_event_logs' indicates retrieval of Windows event log data. No description provided, but the sibling tools and server context show a forensics/incident response pattern where similar-named tools (collect_artifact, collect_file,…
Attacks that exploit this kind of access
windows_event_logs. 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_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 Velociraptor MCP Server. Nothing to install.
windows_event_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 windows_event_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 windows_event_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.
windows_event_logs 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 →