Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_spiderfoot

Destructive

Run SpiderFoot reconnaissance scans inside an isolated engagement namespace to map hosts, domains, and exposed services. Pass argv tokens directly for shell-free execution of OSINT enumeration tasks.

Instructions

Run spiderfoot from the OpenCyber enumeration toolkit. The container executes spiderfoot 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_spiderfoot"
  }
}

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

A3.6/5.0
Behavior4/5

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

Beyond the annotations (destructive, openWorld, non-idempotent), it discloses the key execution model: the container invokes `spiderfoot` directly with the supplied argv and never uses shell parsing, which tells the agent quoting/expansion will not happen. It also states the operation is scoped to the selected engagement namespace. It stops short of saying what gets written/destroyed in the namespace or how long scans may run.

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 the execution model, then the path scoping convention. No filler; a slightly more explicit marker of the argv/working-directory link would have made it tighter still.

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 and annotations are rich, so the description needn't cover return values or safety. However, for a four-parameter CLI wrapper with an arbitrary argv surface and an unexplained `stdin` parameter, it leaves the agent guessing about flag conventions and stdin usage.

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 explains that `arguments` is a raw argv token list (not a shell string) and implies `working_directory` should be relative to the engagement namespace via the artifact-path note. `engagement_id` and especially `stdin` receive no explanation, and no hint is given about where valid spiderfoot flags can be found.

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: run `spiderfoot` from the OpenCyber enumeration toolkit, with argv tokens passed directly to the container. That is clear enough to distinguish it from a generic shell tool like oc_bash, but it does not contrast with neighbouring recon tools (e.g. oc_amass, oc_autorecon), so the sibling differentiation is only partial.

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 implied through 'enumeration toolkit' plus the instruction to run from the selected engagement namespace and use relative paths for engagement artifacts. There is no explicit when-to-use/when-not guidance and no statement of which alternative tool to pick for a given recon task.

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