Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_exiftool

Destructive

Run exiftool directly to extract and inspect file metadata in an isolated engagement workspace; arguments pass as argv tokens without shell parsing for safe forensic analysis.

Instructions

Run exiftool from the OpenCyber forensics toolkit. The container executes exiftool 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_exiftool"
  }
}

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

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful behavior — no shell parsing, argv tokens passed verbatim, execution scoped to the engagement namespace — but it never explains *why* the tool is flagged destructive (e.g., that exiftool can rewrite files in place), which is the most important missing warning.

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 with the execution model front-loaded and no filler. Minor redundancy between 'Run exiftool' and 'executes `exiftool` directly' keeps it just short of ideal.

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 explained, and the annotations carry the risk flags. For a destructive, argument-driven tool, however, the definition should warn about in-place file modification and how stdin interacts with file arguments; that omission leaves the agent under-informed before a write-capable call.

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%, so the description carries the full burden. It clarifies the semantics of 'arguments' (raw argv tokens, no shell interpretation) and 'working_directory' (relative paths resolved against the engagement namespace), but says nothing about 'stdin' or what 'engagement_id' scopes beyond the terse namespace remark, leaving half the parameters undocumented in both places.

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 — 'Run exiftool from the OpenCyber forensics toolkit' — and clarifies the execution mechanism (direct argv, no shell). It does not distinguish this from sibling forensics tools such as oc_binwalk, nor does it say what exiftool is used for (metadata extraction), which is assumed knowledge.

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 context is implied by 'forensics toolkit' and the pointer to engagement-relative paths, but there is no explicit when-to-use, when-not-to-use, or naming of an alternative tool for metadata versus carving/binary analysis. The path guidance is operational 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