Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_censys

Destructive

Execute Censys enumeration commands with supplied arguments in an isolated engagement workspace, avoiding shell parsing and keeping artifacts scoped to the engagement.

Instructions

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

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
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful execution context beyond that: argv tokens are passed without shell parsing and execution is scoped to the engagement namespace. It omits auth/API-key requirements, rate-limit behavior, and what side effects the destructive flag actually implies in this sandbox.

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, front-loaded with the action, then execution semantics, then path/namespace guidance. No filler. A slightly more deliberate ordering (namespace/relative paths before execution details) could improve it marginally.

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 described. However, for a destructive, open-world CLI wrapper with 0% schema description coverage, the definition should still mention credential requirements for Censys and clarify the undocumented `stdin` parameter; as written it is only marginally complete.

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 coverage is 0%, so the schema documents none of the four parameters. The description partially compensates: `arguments` is explained as argv tokens, `working_directory` as the base for relative engagement paths, and `engagement_id` as the namespace selector. `stdin` is never mentioned, leaving one of four parameters with zero documentation anywhere.

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 plus resource: it runs the `censys` binary from the OpenCyber toolkit. An agent knows this is a CLI passthrough for Censys enumeration. It doesn't say what Censys itself is for (certificate/host search) or how it differs from the many other oc_* wrappers, so it falls short of full sibling differentiation.

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 rather than stated: it says to run from the selected engagement namespace and to use relative paths for engagement artifacts, which tells the agent how to invoke it. There is no explicit when-to-use or when-not-to-use guidance, no mention of required Censys API credentials, and no hint of when to prefer a different enumeration sibling.

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