start_evil_winrm

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp

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/halilkirazkaya-pentester-mcp/start-evil-winrm.md

WHAT IT DOES

What start_evil_winrm does on Pentester-MCP

AI agents invoke start_evil_winrm to trigger actions in Pentester-MCP. 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 start_evil_winrm is rated High

This tool enables remote command execution on Windows systems, which is an Execute category action with critical severity due to the potential for arbitrary code execution, full system compromise, lateral movement, and data exfiltration. The 'evil-winrm' tool is specifically designed for post-exploitation access and interactive shell access on compromised or authorized Windows hosts.

From the tool's definition Tool name 'start_evil_winrm' indicates execution of evil-winrm, a penetration testing tool that establishes interactive remote command execution sessions on Windows systems via WinRM protocol.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_evil_winrm safely

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

start_evil_winrm Rate-limited

start_evil_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": {
    "start_evil_winrm": {
      "limits": [
        {
          "counter": "start_evil_winrm_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 Pentester-MCP, apply this rule, and every start_evil_winrm call is checked against it from then on.

FAQ

Questions about start_evil_winrm

What does the start_evil_winrm tool do? +

start_evil_winrm is a execute tool on the Pentester MCP server. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_evil_winrm? +

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

What risk level is start_evil_winrm? +

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

Can I rate-limit start_evil_winrm? +

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

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

start_evil_winrm is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentester, and thousands of servers like it.

This server

All 337 Pentester tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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