Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_request

Destructive

Send an HTTP request and return status, headers, and up to 256 KiB of decompressed body, flagging truncation for larger responses and enforcing engagement scope when enabled.

Instructions

Send an HTTP request and return its status, headers and up to 256 KiB of decompressed response body. Larger bodies report truncation and partial coverage. When OPENCYBER_ENFORCE_SCOPE is on, engagement_id is required and the requested host must be in the engagement targets.

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": {
      "method": "<method>",
      "url": "<url>"
    },
    "name": "oc_http_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
methodYes
headersNo
timeoutNo
engagement_idNo
follow_redirectsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and non-idempotent, so the risk profile is covered. The description adds genuinely new behavior: a hard 256 KiB decompressed-body cap, explicit truncation/partial-coverage reporting, and the scope-enforcement gate on engagement_id and target hosts. Nothing here contradicts the annotations; a destructive outbound request is consistent with destructiveHint=true.

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, zero filler, and the most load-bearing facts (return shape, truncation limit) are front-loaded before the conditional scope rule. Every sentence contributes information an agent would otherwise have to discover by trial.

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?

For a 7-parameter outbound-request tool with an output schema present, this is close to sufficient: return payload, size ceiling, truncation semantics and the scope-enforcement gate are all stated. The remaining gap is that request-shaping parameters (timeout units, body encoding, redirect behavior) are undocumented anywhere, which matters for a tool whose whole job is constructing requests.

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% across 7 parameters, so the description carries the burden and only explains engagement_id (conditional on OPENCYBER_ENFORCE_SCOPE). Method, url, body, headers, timeout and follow_redirects get no added meaning — notably timeout units/default and body encoding are left entirely ambiguous, and those are not safely inferable.

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 ('Send an HTTP request') plus what comes back (status, headers, up to 256 KiB of decompressed body). This is clearly distinguishable in kind from siblings like oc_graphql_request or oc_http_session_create, though the description never explicitly contrasts itself with the many other HTTP-family tools.

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 is only implied: an agent infers this is the generic raw-HTTP tool. There is no statement of when to prefer it over oc_graphql_request, oc_http_repeater, or oc_http_intruder, and no exclusions. The one concrete conditional ('When OPENCYBER_ENFORCE_SCOPE is on, engagement_id is required') is a prerequisite rather than routing 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