Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_x8

Destructive

Executes x8 from the OpenCyber web toolkit using supplied argument tokens in an engagement workspace, without shell parsing and with relative artifact paths.

Instructions

Run x8 from the OpenCyber web toolkit. The container executes x8 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_x8"
  }
}

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

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the risk profile is conveyed structurally. The description adds genuinely useful behavior: argv-token execution with no shell parsing, and engagement-scoped execution. It does not, however, warn about concrete destructive effects or what the engagement namespace implies for side effects.

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, then execution model, then path convention. No filler, though the namespace/path sentence could be folded tighter.

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 no explanation, and the description covers the execution model and namespace well. What remains missing for a destructive external-CLI wrapper is what x8 does, how stdin is used, and any effect on engagement artifacts. Adequate but with clear gaps.

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 has to carry the burden. It implicitly explains 'arguments' as argv tokens, 'engagement_id' as the engagement namespace, and 'working_directory' via the relative-paths note, but it never mentions 'stdin' at all and gives no format details. Partial compensation only.

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

Purpose3/5

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

The description names a specific verb and binary ('Run x8 from the OpenCyber web toolkit'), which separates it from siblings like oc_bash or oc_amass by naming the wrapped tool. However, it never states what x8 actually does or what kind of output to expect, so an agent must already know the x8 CLI to judge relevance. That is vague purpose rather than a clear verb+resource statement.

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?

There is no guidance on when to choose x8 over alternative recon/fuzzing tools in the sibling list, nor any prerequisites or exclusions. The only operational hints are about relative paths and the engagement namespace, which are mechanics rather than selection guidance.

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