persist_wmi

WMI event subscription persistence. 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/persist-wmi.md

WHAT IT DOES

What persist_wmi does on Claude C2

AI agents invoke persist_wmi 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 persist_wmi is rated High

WMI event subscription persistence installs a persistent execution mechanism on a remote system by creating WMI event filters, consumers, and bindings. This causes arbitrary code/commands to execute automatically on the target system whenever trigger conditions are met. Combined with sibling tools like amsi_bypass, bypassuac, and browser_creds, this is clearly a remote access/implant toolkit.

From the tool's definition persist_wmi — WMI event subscription persistence. Auto-selects client.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs persist_wmi 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 persist_wmi, this is the rule to start with:

persist_wmi Rate-limited

persist_wmi 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": {
    "persist_wmi": {
      "limits": [
        {
          "counter": "persist_wmi_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 persist_wmi call is checked against it from then on.

FAQ

Questions about persist_wmi

What does the persist_wmi tool do? +

WMI event subscription persistence. 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 persist_wmi? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for persist_wmi: 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 persist_wmi? +

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

Can I rate-limit persist_wmi? +

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

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

persist_wmi 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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