Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hcitool

Destructive

Runs hcitool commands with argv tokens and no shell parsing inside an engagement namespace, enabling scoped Bluetooth scanning and wireless attack operations.

Instructions

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

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the safety profile is supplied. The description adds genuinely non-obvious behavior: the container executes hcitool directly as an argv vector and 'shell parsing is never used', which tells the agent not to rely on quoting, pipes, or redirection, and that execution is scoped to the selected engagement namespace. It still does not disclose privilege requirements (many hcitool subcommands need raw HCI access) or failure reporting.

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 and binary name, then execution semantics, then path scoping. No filler; the execution-model sentence earns its place. Slight redundancy between 'Runs from the selected engagement namespace' and the relative-path hint.

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?

With an output schema present, return values need not be explained, and the annotations carry the risk profile. However, for a 4-parameter wrapper with zero schema descriptions, the omission of `stdin` semantics and of any privilege/root expectations for hcitool leaves real gaps an agent would need to guess at.

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

Parameters2/5

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

Schema description coverage is 0% across 4 parameters, so the description must compensate and largely does not. It clarifies that `arguments` is a raw argv token array and that `working_directory` is resolved relative to the engagement namespace, but `stdin` is never mentioned and `engagement_id` only indirectly alluded to via 'selected engagement namespace'.

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 gives a specific verb+resource: it runs the `hcitool` binary from the OpenCyber wireless attack toolkit, with argv tokens passed directly. That is unambiguous about what the tool does. It does not, however, distinguish itself from Bluetooth-adjacent siblings such as oc_bluetoothctl, so an agent still has to infer which wrapper to pick.

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 explicit when-to-use or when-not-to-use guidance and no named alternative among the many Bluetooth siblings. The only usage-adjacent statement is 'use relative paths for engagement artifacts', which is a calling convention rather than selection guidance.

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