Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_file

Destructive

Runs the file utility on engagement artifacts using direct argv execution, avoiding shell parsing for controlled file-type identification.

Instructions

Run file from the OpenCyber binary toolkit. The container executes file 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_file"
  }
}

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

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

The key behavioral disclosure — the container executes the binary directly with argv tokens and never performs shell parsing — is valuable and not present in the annotations. The annotations declare destructiveHint=true, and the description never explains what that means. That silence matters for a tool an agent might treat as a safe read. It also does not describe rate limits or whether the operation mutates the working directory.

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 dense sentences with no filler, front-loaded with the action and followed by the execution model. The opening clause lightly restates the tool name, but overall the wording earns its place.

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?

The description covers the execution model and path scoping, and an output schema exists, so return values need no explanation. It remains incomplete for a four-parameter tool with no parameter documentation, because stdin behavior and the meaning of the destructive annotation are unaddressed.

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 only partly does. It clarifies that `arguments` are argv tokens and that `working_directory` should use relative paths inside the engagement namespace. It says nothing about `engagement_id` scoping semantics or `stdin` handling.

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 states a specific verb and resource: it runs the `file` utility from the OpenCyber binary toolkit. It does not explain in words what `file` returns, but the operation is identifiable. It is distinguishable from oc_file_hashes and oc_file_triage only if the agent already knows that `file` means type identification.

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 description tells the agent how to invoke the tool, not when to use it. It gives no context for choosing this tool over oc_file_hashes or oc_file_triage, which are close alternatives for inspecting files. It also states no prerequisites beyond the implicit need for an engagement namespace.

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