Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_evil_winrm

Destructive

Runs evil-winrm commands within an engagement namespace, passing supplied arguments and optional stdin to support authorized WinRM remote administration and testing.

Instructions

Run evil winrm from the OpenCyber credentials toolkit. The container executes evil-winrm directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_evil_winrm"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag it as destructive, open-world, and non-idempotent; the description adds genuinely new execution semantics — direct argv invocation with no shell parsing, and namespace-scoped working directory. It stops short of noting credential handling or that failures may leave remote state changed, but the added context is real.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the identity of the tool and the invocation model. No filler, though the opening clause slightly restates the name and title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. However, for a destructive, open-world execution tool with two undocumented parameters, the definition should say more about credential expectations and the meaning of `stdin`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It clarifies the `arguments` array as raw argv tokens and ties `working_directory` to relative engagement-artifact paths, but `engagement_id` and especially `stdin` receive no explanation, leaving half the parameters opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb ('Run') plus the specific binary ('evil-winrm') and the toolkit context, so the agent knows exactly which external tool is executed. The note that argv tokens are passed without shell parsing implicitly separates it from a generic shell executor such as oc_bash, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives operating guidance ('runs from the selected engagement namespace', 'use relative paths for engagement artifacts') but never states when to prefer this over a shell tool or what prerequisites (valid credentials, reachable WinRM endpoint) exist. Usage is implied by the tool's purpose rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools