Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rpcclient

Destructive

Runs rpcclient with the supplied arguments for remote Windows RPC enumeration, executing directly without shell parsing inside an isolated engagement namespace workspace.

Instructions

Run rpcclient from the OpenCyber enumeration toolkit. The container executes rpcclient 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_rpcclient"
  }
}

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

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotence, but the description adds real execution semantics beyond them: argv tokens are passed straight to the binary and shell parsing is never used, and execution is scoped to the engagement namespace. That meaningfully changes how an agent should construct a call. It stops short of describing output shape or the consequences of the destructive flag.

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 tight sentences, each doing distinct work, with the execution model front-loaded. No filler or redundancy; slightly more structure (e.g. separating operational constraints) would help but nothing is wasted.

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 explained, and annotations cover the safety profile. However, for a tool that executes an arbitrary argv against a namespace, the description says nothing about required credentials, whether the engagement must be in a particular state, or what stdin is for.

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 description coverage is 0%, so the description must carry the load. It does explain three of the four parameters in prose: 'arguments' are argv tokens (no shell interpretation), 'working_directory' via the relative-paths instruction, and 'engagement_id' via the engagement namespace. 'stdin' is never mentioned, leaving one parameter completely undocumented.

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 specific verb ('Run') and names the exact underlying binary, rpcclient, so an agent knows this is a pass-through wrapper for that tool. It does not explain what rpcclient does (SMB enumeration) or differentiate it from the many other oc_* tool wrappers, but the identity is unambiguous.

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

Usage Guidelines2/5

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

The description never says when to reach for rpcclient versus a sibling enumerator, nor what prerequisites must be satisfied first. The only guidance offered is operational ('runs from the selected engagement namespace; use relative paths'), which is about how to invoke it, not when to choose it.

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