Clear a Windows Event Log (requires admin privileges)
AI agents call event_log_clear to permanently remove resources in Mcp Windows — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes Windows Event Log entries, which constitutes irreversible destruction of data. Event logs are critical for security auditing, compliance, and forensic investigation. An AI agent misusing this tool could destroy evidence of malicious activity, violate compliance requirements (SOC2, HIPAA, etc.), or hide system compromise.
From the tool's definition Tool name 'event_log_clear' and description 'Clear a Windows Event Log' indicate irreversible deletion of event log data. Clearing event logs destroys audit trails and forensic evidence that cannot be recovered.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access event_log_clear gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for event_log_clear:
{
"version": "1",
"default": "deny",
"hide": [
"event_log_clear"
]
} event_log_clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear a Windows Event Log (requires admin privileges). It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for event_log_clear: 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 Mcp Windows. Nothing to install.
event_log_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the event_log_clear 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_log_clear. 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_log_clear is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.