Comprehensive Windows Event Viewer tool that combines search and analysis capabilities. Can enumerate ALL available Windows event logs and search across them for keywords, event IDs, or other criteria, while also providing detailed security analysis, error pattern detection, and actionable recomm...
AI agents call event_viewer to retrieve information from Windows Diagnostics 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 and queries diagnostic data (event logs, security information, error patterns) without altering system state. While it provides comprehensive access to system diagnostic information that could inform an attacker about system vulnerabilities, it is fundamentally a read-only inspection tool. The 'detailed security analysis' is analytical output, not system manipulation.
From the tool's definition Tool performs 'enumerate', 'search', and 'analysis' of existing Windows event logs with no modification or deletion capabilities mentioned.
Attacks that exploit this kind of access
Comprehensive Windows Event Viewer tool that combines search and analysis capabilities. Can enumerate ALL available Windows event logs and search across them for keywords, event IDs, or other criteria, while also providing detailed security analysis, error pattern detection, and actionable recommendations. It is categorised as a Read tool in the Windows Diagnostics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows Diagnostics MCP Server MCP server in PolicyLayer and add a rule for event_viewer: 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 Windows Diagnostics MCP Server. Nothing to install.
event_viewer 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 event_viewer 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 event_viewer. 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.
event_viewer is provided by the Windows Diagnostics MCP Server MCP server (jackalterman/windows-diagnostic-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 →