Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_packet_capture

Destructive

Capture network packets by running tcpdump with explicit argv tokens in an engagement namespace, avoiding shell parsing and storing relative-path artifacts in the workspace.

Instructions

Run packet capture from the OpenCyber network toolkit. The container executes tcpdump 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_packet_capture"
  }
}

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent; the description adds real context beyond them: the container invokes tcpdump directly with pre-tokenized argv and never uses shell parsing, and execution is scoped to the selected engagement namespace. It stops short of saying what artifacts get written or whether existing capture files are overwritten, which matters given the destructive hint.

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 core action and followed by the two constraints that most affect correct invocation (tokenized argv, relative paths). 'From the OpenCyber network toolkit' is mild filler but sets the product context cheaply.

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 capture tool the description omits where capture output lands, whether the agent must pass an output filename in 'arguments', and what existing data could be affected — gaps that matter given the annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description does substantial work: 'arguments' is explained as argv tokens with no shell parsing (implying no quoting or shell metacharacters), 'working_directory' is addressed via the relative-path instruction, and 'engagement_id' is implied by 'runs from the selected engagement namespace.' The 'stdin' parameter is never mentioned, so full compensation is not achieved.

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 packet capture') and names the underlying utility ('tcpdump'), which tells an agent exactly what execution engine backs this tool. It does not differentiate itself from the sibling oc_packet_analysis (analyze vs. capture), so the agent must infer that distinction from names alone.

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 guidance is limited to mechanics ('use relative paths for engagement artifacts') rather than when this tool is appropriate versus alternatives. There is no statement of prerequisites, no mention of requiring elevated privileges for tcpdump, and no explicit exclusion or pointer to a sibling for post-capture analysis.

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