etw_patch

Patch ETW logging. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xyg3n-claude-c2/etw-patch.md

WHAT IT DOES

What etw_patch does on Claude C2

AI agents invoke etw_patch to trigger actions in Claude C2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why etw_patch is rated High

Patching ETW is a well-known defense evasion technique that disables Windows security event logging, blinding EDR/AV/SIEM solutions. This is an Execute-class action (modifying runtime behavior of a system process/mechanism), but given the server context (amsi_bypass, bypassuac, browser_creds siblings) and the irreversible nature of the in-memory patch during a session, it is critically severe.

From the tool's definition 'Patch ETW logging' — ETW (Event Tracing for Windows) is a core Windows security and diagnostic logging mechanism. Patching it disables or tampers with security telemetry.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs etw_patch safely

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

etw_patch Rate-limited

etw_patch stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "etw_patch": {
      "limits": [
        {
          "counter": "etw_patch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every etw_patch call is checked against it from then on.

FAQ

Questions about etw_patch

What does the etw_patch tool do? +

Patch ETW logging. Auto-selects client. It is categorised as a Execute tool in the Claude C2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on etw_patch? +

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

What risk level is etw_patch? +

etw_patch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit etw_patch? +

Yes. Add a rate_limit block to the etw_patch 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 etw_patch completely? +

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

etw_patch is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools → High-risk tools on this server →

Across the catalogue

start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →