Query a Windows event log via Get-WinEvent FilterHashtable.
AI agents call query_event_log to retrieve information from Procmon 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 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.
Documented attack patterns abuse exactly the kind of access query_event_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Procmon, and nothing reaches the server without passing your rules. This is the rule we recommend for query_event_log:
{
"version": "1",
"default": "deny",
"tools": {
"query_event_log": {}
}
}query_event_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
query_event_log 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 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.
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.
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.
Deterministic rules across all 18 Procmon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Procmon tools catalogued and risk-classified — across an index of 42,500+ MCP servers.