Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_sherlock

Destructive

Runs username enumeration across online services to identify existing accounts, executing supplied arguments directly without shell parsing inside an isolated engagement workspace.

Instructions

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

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

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

Annotations already declare destructive, openWorld, non-idempotent and non-readOnly, so the safety profile is covered. The description adds genuinely new behavioral facts: argv tokens are passed directly with no shell parsing (a security-relevant guarantee) and execution is scoped to the engagement namespace. It stops short of noting rate limits, network egress, or runtime duration, which matter for an open-world enumeration 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 short sentences, front-loaded with the action, then the execution model, then the path convention. No filler, though the middle sentence's shell-parsing detail could be tightened.

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 the annotations carry the risk profile. However, for a destructive open-world tool with 0% schema coverage, the description omits what sherlock actually produces, how stdin is consumed, and any runtime or rate-limit expectations.

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 compensate. It clarifies that 'arguments' are raw argv tokens and that paths should be relative to the engagement namespace, which covers two of the four parameters. The 'stdin' and 'working_directory' parameters are never mentioned, leaving half the surface undocumented.

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 ('Run sherlock from the OpenCyber enumeration toolkit') and identifies it as a direct wrapper, which distinguishes it from the many other oc_* wrappers. It does not say what sherlock itself does (username enumeration across sites), so an agent unfamiliar with the binary gets no functional summary.

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?

The description gives execution context ('runs from the selected engagement namespace; use relative paths') but never says when to choose this tool over siblings or what preconditions apply. No exclusions or alternatives are named, leaving selection entirely to the agent's prior knowledge of sherlock.

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