Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_subzy

Destructive

Check domains for subdomain takeover vulnerabilities by running subzy with supplied arguments in an engagement workspace; arguments execute directly without shell parsing.

Instructions

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

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

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered by structured data. The description adds genuinely useful behavior: arguments are passed as raw argv tokens with no shell parsing (so no quoting/injection concerns) and execution is scoped to an engagement namespace. It does not disclose what gets modified on disk, whether results persist, or any rate/timeout behavior, which matters for a destructive open-world binary.

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 the execution contract front-loaded and no filler. The engagement-scoping note follows logically. Slightly under-specified rather than verbose, but nothing in it is wasted.

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 destructive/open-world nature is covered by annotations. What remains missing is the one thing an agent most needs: what the binary does and when to reach for it instead of a sibling recon tool. Adequate as a generic wrapper, incomplete as a selection aid.

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, and it partially does: it clarifies that `arguments` are argv tokens (not a shell string) and that `working_directory` should be relative within the engagement namespace. However, `stdin` is never mentioned, and there is no example of typical argument form (e.g. target flags) or how `engagement_id` affects execution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Run subzy from the OpenCyber web toolkit" essentially restates the tool name oc_subzy and never says what subzy actually does (subdomain takeover detection) or what the tool returns. The only added information is execution mechanics (argv tokens, no shell parsing), which describes how it runs rather than its purpose. An agent unfamiliar with the binary learns nothing about the capability.

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 guidance, no prerequisites, and no routing to alternatives among the many sibling recon tools (oc_amass, oc_autorecon, etc.). The mention of running "from the selected engagement namespace" is a scoping note, not usage guidance. An agent must already know what subzy is to know when to select it.

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