get_security_events

What get_security_events does on Procmon

AI agents call get_security_events 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 get_security_events is rated Low

This tool retrieves historical security event log data from Windows event logs. While it requires administrative elevation and the events themselves contain sensitive information (process creation, logon events, privileged operations), the operation is fundamentally a query/read operation with no side effects. It does not create, modify, delete, or execute anything—it only accesses and returns existing event data.

From the tool's definition Tool name 'get_security_events' and description indicate retrieval of security event logs (IDs 4688, 4624, 4672, 4648). These are Windows security log event IDs that are queried/retrieved, not modified or executed.

The rule that runs get_security_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Procmon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_security_events, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_security_events": {}
  }
}

Questions about get_security_events