evil_winrm_connect

evil_winrm_connect

Server Kali Linux MCP Server ofryma/custom-mcp-library
Category Execute
Risk class High
Parameters 00 required

What evil_winrm_connect does on Kali Linux MCP Server

AI agents invoke evil_winrm_connect to trigger actions in Kali Linux 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 evil_winrm_connect needs a policy

EvilWinRM is a post-exploitation tool that connects to Windows Remote Management endpoints and provides an interactive shell. This constitutes remote code execution on target systems. Given the server context (Kali Linux pen-testing server with exploitation frameworks), this tool almost certainly enables arbitrary command execution on remote Windows hosts.

From the tool's definition Tool name 'evil_winrm_connect' — 'evil_winrm' is a well-known penetration testing tool used to establish WinRM (Windows Remote Management) shells on target systems, enabling remote command execution on Windows machines.

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 Kali Linux 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 evil_winrm_connect? +

Register the Kali Linux MCP 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 Kali Linux MCP 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 Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.