cme_winrm · CrackMapExec MCP Server MCP: Risk & Policy

WHAT IT DOES

What cme_winrm does on CrackMapExec MCP Server

AI agents invoke cme_winrm 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_winrm needs a policy

cme_winrm performs remote command execution on WinRM-enabled hosts, which is a classic Execute capability. It also supports credential dumping, which involves extracting sensitive authentication material from running systems. The combination of arbitrary remote command execution (whose effects depend on arguments) and system-level credential access makes this critical severity.

From the tool's definition 'Execute WinRM protocol operations. Supports remote command execution and credential dumping on hosts with WinRM enabled (ports 5985/5986).' The tool explicitly performs remote command execution and credential dumping, both of which are Execute-class…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cme_winrm Rate-limited

cme_winrm 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_winrm": {
      "limits": [
        {
          "counter": "cme_winrm_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_winrm

What does the cme_winrm tool do? +

Execute WinRM protocol operations. Supports remote command execution and credential dumping on hosts with WinRM enabled (ports 5985/5986). 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_winrm? +

Register the CrackMapExec MCP Server MCP server in PolicyLayer and add a rule for cme_winrm: 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_winrm? +

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

Can I rate-limit cme_winrm? +

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

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

cme_winrm 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.