query_event_log

Query a Windows event log via Get-WinEvent FilterHashtable.

SERVERProcmon SOURCE0xhackerfren/procmon-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xhackerfren-procmon-mcp/query-event-log.md

What query_event_log does on Procmon

AI agents call query_event_log to retrieve information from Procmon without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why query_event_log is rated Low

This tool retrieves and queries Windows event log entries using the Get-WinEvent cmdlet. No data is created, modified, deleted, or executed. However, event logs may contain sensitive security information (authentication failures, privilege escalation attempts, etc.), so unauthorized or excessive querying could expose confidential data or support reconnaissance for attacking a system.

From the tool's definition Tool name 'query_event_log' and description 'Query a Windows event log via Get-WinEvent FilterHashtable' indicate a read-only operation that retrieves event log data without modification.

Questions about query_event_log

What does the query_event_log tool do? +

Query a Windows event log via Get-WinEvent FilterHashtable. It is categorised as a Read tool in the Procmon MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_event_log? +

Register the Procmon MCP server in PolicyLayer and add a rule for query_event_log: 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 Procmon. Nothing to install.

What risk level is query_event_log? +

query_event_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_event_log? +

Yes. Add a rate_limit block to the query_event_log 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.

How do I block query_event_log completely? +

Set action: deny in the PolicyLayer policy for query_event_log. 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.

What MCP server provides query_event_log? +

query_event_log is provided by the Procmon MCP server (0xhackerfren/procmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Procmon, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Procmon's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.