Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_sleuthkit_icat

Destructive

Extract file contents from forensic disk images by running Sleuth Kit icat with supplied arguments in an isolated engagement workspace.

Instructions

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

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, readOnlyHint=false, and idempotentHint=false. The description adds genuinely useful execution semantics not in the annotations: arguments are passed as argv tokens with no shell parsing, and paths resolve relative to the engagement namespace. It does not address the notable risk that output may be raw binary file content, nor why a content-extraction read is flagged destructive.

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 immediately followed by the security-relevant execution detail; no filler or redundant restatement of the title beyond the opening clause.

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-value explanation is not needed. But for a 4-parameter, 0%-schema-coverage tool with destructiveHint=true, the definition leaves an agent without enough to form correct argv (inode, offset, image path) or to know what comes back, which matters greatly for a binary content extractor.

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 carry the semantics, and it only partly does: 'arguments' are described as argv tokens, 'working_directory' is implied by the relative-path note, and 'engagement_id' is implied by the namespace sentence. The 'stdin' parameter is never mentioned, and no example argv shape for icat (image path plus inode) is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Run sleuthkit icat') but effectively restates the tool name rather than explaining the resource: it never says icat extracts file content by inode from a forensic disk image. Its only real differentiation from a generic exec tool is the execution model (direct argv, no shell), not what the tool actually does forensically.

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?

It says the tool runs in the selected engagement namespace and to use relative paths, which implies usage context. However, it gives no guidance on when to choose icat over the sibling oc_sleuthkit_fls (i.e., list inodes first, then extract a specific inode's content), no note about required disk-image path or inode argument, and no exclusions.

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