evil_winrm_connect | PolicyLayer

WHAT IT DOES

What evil_winrm_connect does on K-MCP: Kali Model Context Protocol Server

AI agents invoke evil_winrm_connect to trigger actions in K-MCP: Kali Model Context Protocol 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 evil_winrm_connect needs a policy

Evil-WinRM is a penetration testing tool that connects to Windows Remote Management (WinRM) services to provide an interactive shell. This constitutes executing remote commands on target systems. The server context (Kali Linux, penetration testing, CTF) and sibling tools (hydra_attack, john_crack) confirm offensive use.

From the tool's definition Tool name 'evil_winrm_connect' on a Kali Linux MCP server alongside tools like 'hydra_attack', 'john_crack', and 'execute_command'. Evil-WinRM is a well-known offensive security tool used to establish remote shell sessions on Windows machines via WinRM.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

evil_winrm_connect Rate-limited

evil_winrm_connect 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": {
    "evil_winrm_connect": {
      "limits": [
        {
          "counter": "evil_winrm_connect_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 K-MCP: Kali Model Context Protocol Server, so you can run agents against it safely.

FAQ

Questions about evil_winrm_connect

What does the evil_winrm_connect tool do? +

evil_winrm_connect. It is categorised as a Execute tool in the K-MCP: Kali Model Context Protocol 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 evil_winrm_connect? +

Register the K-MCP: Kali Model Context Protocol Server MCP server in PolicyLayer and add a rule for evil_winrm_connect: 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 K-MCP: Kali Model Context Protocol Server. Nothing to install.

What risk level is evil_winrm_connect? +

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

Can I rate-limit evil_winrm_connect? +

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

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

evil_winrm_connect is provided by the K-MCP: Kali Model Context Protocol Server MCP server (stoicmehedi/k-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.