Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_socat

Destructive

Run socat with explicit arguments in an engagement workspace to create relays, forward ports, or test connections without shell parsing.

Instructions

Run socat from the OpenCyber network toolkit. The container executes socat 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_socat"
  }
}

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.8/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-idempotent, so the safety profile is covered. The description adds genuinely useful behavior beyond that: argv tokens are passed directly with no shell parsing, which tells the agent that pipes, redirects, and metacharacters will not work, and that execution is scoped to the engagement namespace.

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

Conciseness5/5

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

Three short sentences, front-loaded with what runs, followed by the two constraints that matter most (no shell parsing, namespace-relative paths). No filler.

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

Completeness4/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. For a four-parameter execution wrapper the description covers the critical invocation semantics; the only real gap is the undocumented stdin parameter and the default working directory.

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 compensate. It clarifies that 'arguments' are raw argv tokens (not a shell string) and that paths are relative to the engagement namespace, covering engagement_id and working_directory implicitly, but it says nothing about the 'stdin' parameter or the default working directory.

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 and resource ('Run socat from the OpenCyber network toolkit'), which is concrete enough for an agent to know exactly what executes. It does not explicitly differentiate itself from other oc_* network tools, but the named binary is itself the distinguishing element.

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?

Provides operational context ('Runs from the selected engagement namespace; use relative paths for engagement artifacts') but never states when to choose socat over a sibling tool or when not to use it. Usage is implied by the tool name rather than argued.

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