Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rustscan

Destructive

Execute RustScan directly with supplied arguments in an isolated engagement namespace to perform scoped network port discovery without shell parsing.

Instructions

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

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
Behavior3/5

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

Annotations already declare destructive=true, openWorld=true, and non-idempotent, so the risk profile is covered structurally. The description adds genuine behavioral context beyond that: raw argv invocation without shell parsing, execution scoped to the engagement namespace, and relative-path expectations. It does not explain rate limits, target impact, or what happens on failure, so it is additive but not rich.

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 action and followed by the two operational constraints that actually matter. No filler or repetition, though the path guidance could be folded more tightly into the execution sentence.

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

Completeness5/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 no explanation, and annotations carry the safety profile. For a thin argv-wrapper tool the remaining essentials (execution model, namespace scoping, relative paths) are covered, leaving only minor unaddressed details like the stdin parameter.

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%, but the description compensates partially by clarifying that 'arguments' are argv tokens passed directly (not a shell string) and that 'working_directory' should use relative paths within the engagement namespace. The 'stdin' parameter and the format/meaning of engagement_id are never addressed, leaving a meaningful gap for a 4-parameter tool.

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?

The description states a specific verb and resource ('Run rustscan') and implicitly distinguishes itself from the generic oc_bash sibling by noting that the container executes rustscan directly with argv tokens and never uses shell parsing. It stops short of naming an alternative tool explicitly, but the purpose 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 gives operating context (engagement namespace, relative paths) but no guidance on when to choose this over oc_bash or another scanner, no prerequisites, and no exclusions. An agent must infer the usage scenario entirely from the tool name.

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