Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hakrawler

Destructive

Run web crawler commands with supplied arguments inside an isolated engagement workspace to collect URLs from authorized targets; inputs bypass shell parsing.

Instructions

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

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.1/5.0
Behavior4/5

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

Annotations already declare destructive/openWorld/non-idempotent, so the safety profile is covered; the description adds genuinely useful non-obvious behavior: execution is argv-based with no shell parsing (so no pipes, globs, or metacharacters) and it runs scoped to the selected engagement namespace. It does not mention external network reach or rate/load implications, which would matter for an openWorld tool.

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 tight sentences with no filler, and the execution-model detail is front-loaded ahead of the namespace/path note. Nothing redundant is present.

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 not be explained, and the execution model is described. However, for a destructive, open-world tool with four undocumented schema parameters, the definition omits what the tool produces, how stdin is consumed, and any caution about contacting target hosts.

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 must carry parameter meaning. It implicitly covers three of four parameters (argv tokens = arguments, engagement namespace = engagement_id, relative paths = working_directory) but says nothing about stdin, leaving one required piece of the interface undocumented in both schema and text.

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 verb and resource are stated ('Run hakrawler from the OpenCyber web toolkit'), but the description never says what hakrawler actually does (crawling URLs / extracting endpoints) nor how it differs from dozens of sibling oc_* wrappers such as oc_amass or oc_autorecon. An agent that doesn't already know the binary gets little functional definition.

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 when-to-use or when-not-to-use guidance and no named alternative. The only guidance is procedural ('use relative paths for engagement artifacts'), which is invocation detail rather than tool selection advice.

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