Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_kismet

Destructive

Execute Kismet wireless toolkit commands within an isolated engagement namespace using supplied argv tokens, with no shell parsing and relative paths for engagement artifacts.

Instructions

Run kismet from the OpenCyber wireless toolkit. The container executes kismet 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_kismet"
  }
}

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

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

The annotations already disclose the risk profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), so the description only needs to add context. It does add one genuinely useful behavioral fact: argv is passed directly and shell parsing is never used, which tells the agent not to quote or chain commands. However, it says nothing about runtime duration, capture-output handling, or what a destructive run actually affects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying distinct information: identity, execution semantics, and path context. The most decision-relevant fact (direct argv execution, no shell) is front-loaded and there is no filler.

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. However, for a tool that runs an arbitrary destructive wireless binary, the definition leaves engagement_id and stdin semantics unexplained and gives no sense of what the binary does or when a run is appropriate, which is a real gap for an exec wrapper with four undocumented parameters.

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% across four parameters, so the description must compensate. The passing of 'arguments' as raw argv tokens with no shell parsing is a meaningful clarification beyond the bare array type, and 'use relative paths for engagement artifacts' partially explains working_directory. But engagement_id and stdin are entirely undefined in both schema and description.

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 names a specific verb and resource: it runs `kismet` from the OpenCyber wireless toolkit, and it clarifies that the container executes the binary directly rather than through a shell. This tells an agent exactly what happens, though it never explains what kismet itself does or why an agent would pick it over the other wireless siblings such as oc_airodump or oc_airmon.

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 only guidance is operational (engagement namespace, relative artifact paths, argv tokens), not selection guidance. Nothing states when this tool is appropriate versus oc_airodump, oc_airmon, or oc_arp_scan, and no prerequisites, exclusions, or permission requirements are mentioned.

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