Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_httpx

Destructive

Runs httpx with explicit argv tokens in an engagement workspace to perform HTTP probing and write results to relative engagement artifacts without shell parsing.

Instructions

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

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.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is covered. The description adds real value beyond that: argv tokens are passed literally with no shell parsing, and execution is scoped to the selected engagement namespace. It does not say what happens on failure or how long a run may take.

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 execution model, then the namespace context. No filler; each sentence contributes something. Minor redundancy between the namespace statement and the relative-path guidance.

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 annotations cover the safety profile. What remains missing is guidance on when to reach for this tool versus a generic shell sibling, and any meaning for `engagement_id` or `stdin`, which an agent must guess at.

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

Parameters2/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 parameter meaning. It clarifies only `arguments` (literal argv tokens, no shell interpretation) and indirectly `working_directory` via the relative-path note. `engagement_id` and `stdin` are never explained, leaving two of four parameters undocumented anywhere.

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 and resource: run `httpx` from the OpenCyber web toolkit, executed directly in the container. The agent knows exactly what will run. It stops short of distinguishing this from the many other execution-style siblings (e.g. oc_bash), so it is clear but not fully differentiated.

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?

Usage context is only implied: this is the way to invoke httpx. The one explicit guideline — use relative paths for engagement artifacts — is about path handling, not tool selection. Nothing tells the agent when to choose this over oc_bash or another recon sibling, and there are no prerequisites stated.

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