Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_usbguard

Destructive

Inspect and enforce USB device authorization policy within an engagement namespace, using relative paths for artifacts. Control which USB devices are permitted.

Instructions

Inspect and enforce USB device authorization policy. 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_usbguard"
  }
}

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.9/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 risk profile is covered by structured data. The description adds real context beyond that: the tool executes within the selected engagement namespace and artifact paths are relative to it. It does not, however, disclose that the 'arguments' array is passed through to the underlying usbguard CLI, which is the single most important behavioral fact for correct invocation.

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?

Two short sentences, front-loaded with the purpose before the environmental caveat. There is no filler, though the second sentence reads as a fragment whose referent (which artifacts, which paths) is left implicit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the tool is a destructive, open-world CLI passthrough with four undocumented parameters and the description never establishes that contract. An agent could not reliably construct a call from this definition alone without inspecting the schema and guessing at the argument convention.

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 four parameters, so the description must compensate and largely does not. 'Use relative paths for engagement artifacts' loosely implies the working_directory semantics, but engagement_id, stdin, and the arguments array receive no explanation at all; an agent cannot infer from the description that 'arguments' is a raw CLI argument vector.

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 uses a specific verb pair plus resource: 'Inspect and enforce USB device authorization policy.' That tells an agent precisely what domain the tool covers. It stops short of distinguishing itself from any sibling or of naming what 'enforce' means operationally, so it is clear but not differentiating.

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 or when-not-to-use guidance and no named alternative among the many sibling tools. The only operational guidance given is environmental ('runs from the selected engagement namespace; use relative paths'), which is about invocation context rather than tool selection.

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