Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_foremost

Destructive

Recover files from disk images by running Foremost file-carving scans with supplied arguments inside an isolated engagement workspace, without shell parsing.

Instructions

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

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

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

Annotations already declare destructive=true, non-idempotent, and closed-world, so the safety profile is known. The description adds useful execution context—argv tokens are passed directly and shell parsing is never used—but it does not disclose what files may be written or overwritten during a destructive carve, nor where output lands.

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 tight sentences, front-loaded with the action and free of filler. The path guidance is appended after the execution detail, keeping the essential context easy to scan.

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?

For a destructive wrapper around an external binary with four undocumented parameters, the definition is too sparse. It omits what foremost does, what 'destructive' entails in this context, and parameter guidance; the output schema covers return values, but core invocation context is missing.

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 must explain the four parameters. It only alludes to arguments as argv tokens and to paths being relative to the engagement namespace; it says nothing about stdin, working_directory, or the meaning of engagement_id, leaving most parameter semantics undocumented.

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 names the action ('Run foremost') and identifies the toolkit, giving a specific verb and binary name. However, it never explains what foremost actually does—file carving/recovery from disk images—so an agent unfamiliar with the tool cannot infer its purpose from the description alone.

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?

It provides path guidance ('use relative paths for engagement artifacts') and namespace context, but gives no indication of when to select foremost over sibling forensics tools such as binwalk or when not to use it. Usage is only implied by the tool name.

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