cme_wmi · CrackMapExec MCP Server MCP: Risk & Policy

WHAT IT DOES

What cme_wmi does on CrackMapExec MCP Server

AI agents invoke cme_wmi to trigger actions in CrackMapExec MCP Server. 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.

WHY IT NEEDS A POLICY

Why cme_wmi needs a policy

This tool enables remote command execution on Windows systems via WMI (Windows Management Instrumentation), allowing an AI agent to run arbitrary commands on target machines. This is a classic Execute category tool with critical severity due to the ability to compromise remote systems, exfiltrate data, install malware, or pivot through networks.

From the tool's definition Tool description explicitly states 'Execute WMI protocol operations' and 'remote command execution via WMI'. The tool name 'cme_wmi' combined with capabilities for remote command execution indicates arbitrary code execution on remote systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cme_wmi Rate-limited

cme_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": {
    "cme_wmi": {
      "limits": [
        {
          "counter": "cme_wmi_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CrackMapExec MCP Server, so you can run agents against it safely.

FAQ

Questions about cme_wmi

What does the cme_wmi tool do? +

Execute WMI protocol operations. Supports remote command execution via WMI. It is categorised as a Execute tool in the CrackMapExec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cme_wmi? +

Register the CrackMapExec MCP Server MCP server in PolicyLayer and add a rule for cme_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 CrackMapExec MCP Server. Nothing to install.

What risk level is cme_wmi? +

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

Can I rate-limit cme_wmi? +

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

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

cme_wmi is provided by the CrackMapExec MCP Server MCP server (schwarztim/sec-crackmapexec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.