Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_volatility

Destructive

Execute Volatility memory-forensics commands with argv tokens in an engagement workspace to analyze memory artifacts without shell parsing.

Instructions

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

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

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

Annotations already declare destructiveHint=true, non-idempotent and non-read-only, and the description adds genuinely useful behavior: argv is passed directly with no shell parsing, and execution is scoped to the engagement namespace. It does not explain what makes the call destructive (e.g. whether vol writes output files, overwrites artifacts, or consumes significant resources), which is the key gap given destructiveHint=true.

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 identity of the tool and then the two facts that matter (no shell parsing, engagement-relative paths). No filler, though the phrasing is slightly dense with backticks and jargon.

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 described, and the namespace/argv semantics are covered. However, for a destructive 4-parameter tool with zero schema documentation, leaving `stdin` undocumented and not stating what side effects occur is a meaningful incompleteness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 carries the burden. It adds real meaning for `arguments` (raw argv tokens, never shell-parsed) and for `working_directory`/`engagement_id` (relative paths resolve within the engagement namespace), but says nothing about `stdin` or the expected format of engagement_id.

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?

States a specific verb and resource: run the volatility (`vol`) forensics binary from the OpenCyber toolkit. That is clearly distinguishable from the network/browser/radio siblings in the catalog. It stops short of naming a sibling alternative, but the purpose itself is unambiguous.

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?

Gives operational context — runs inside the selected engagement namespace and relative paths should be used for engagement artifacts — but never states when to choose volatility over another forensics tool, nor any preconditions such as needing a memory image present in the engagement.

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