Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_repeater

Destructive

Replay a crafted HTTP request in an engagement session to enforce scope, apply persisted headers, cookies, and match/replace rules, and retain complete evidence.

Instructions

Replay one crafted HTTP request through an engagement workbench session, enforcing scope and applying persisted headers, cookies, and match/replace rules. Complete evidence is retained.

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>",
      "session_id": "<session_id>",
      "method": "<method>",
      "url": "<url>"
    },
    "name": "oc_http_repeater"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
methodYes
headersNo
timeoutNo
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already disclose that this is destructive, open-world, non-idempotent, and not read-only. The description adds useful behavioral context beyond that: scope enforcement, application of persisted headers/cookies/match-replace rules, and retention of complete evidence. It does not explain side effects or authorization requirements in detail, but the added context is substantial.

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?

The definition is two tight sentences with no wasted wording, and the core purpose is front-loaded before the behavioral details. Both sentences contribute useful information.

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?

For a 7-parameter destructive, open-world tool, the description covers purpose and key behavioral traits reasonably well, and the output schema plus annotations reduce some burden. However, with 0% schema parameter descriptions, the complete lack of parameter semantics leaves a clear gap for correct invocation.

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 must compensate, but it does not explain any parameter names or meanings. It vaguely refers to a 'crafted HTTP request' and persisted headers/cookies, but does not clarify required IDs, method/url/body semantics, timeout units, or whether supplied headers override persisted ones.

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: 'Replay one crafted HTTP request through an engagement workbench session.' This clearly identifies the core operation, but it does not explicitly differentiate the tool from siblings such as oc_http_request, oc_http_intruder, or oc_http_history.

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?

The phrase 'through an engagement workbench session' implies usage context, but the description gives no explicit when-to-use or when-not-to-use guidance and does not mention alternatives. An agent can infer this is for replaying within an engagement session, but routing between sibling HTTP tools remains ambiguous.

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