Search events from EVTX file. Filter by time, Event ID, keywords, provider. Supports pagination with offset.
AI agents call evtx_search to retrieve information from Windows Forensics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
evtx_search retrieves and queries event log data without creating, modifying, or deleting records. It is a read-only forensic analysis tool. The severity is low because forensic log queries have minimal blast radius—they cannot alter system state or compromise security directly, though they do access sensitive audit/security information.
From the tool's definition Tool performs search and filtering operations on EVTX (Windows Event Log) files with pagination support. The verb 'search' and the filtering parameters (time, Event ID, keywords, provider) indicate data retrieval with no modification or deletion of logs.
Documented attack patterns abuse exactly the kind of access evtx_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Windows Forensics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for evtx_search:
{
"version": "1",
"default": "deny",
"tools": {
"evtx_search": {}
}
}evtx_search 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.
Search events from EVTX file. Filter by time, Event ID, keywords, provider. Supports pagination with offset. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows Forensics MCP Server MCP server in PolicyLayer and add a rule for evtx_search: 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 Forensics MCP Server. Nothing to install.
evtx_search 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 evtx_search 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 evtx_search. 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.
evtx_search is provided by the Windows Forensics MCP Server MCP server (x746b/winforensics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Windows Forensics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Windows Forensics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.