Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_mfcuk

Destructive

Recovers MIFARE Classic keys via darkside attack when nested authentication fails, running within the selected engagement namespace and using relative paths for engagement artifacts.

Instructions

Recover MIFARE Classic keys with the darkside attack when nested auth fails. 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_mfcuk"
  }
}

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, openWorldHint=true, non-idempotent and non-read-only, so the agent knows this is a risky real-world operation. The description adds useful operational context about running inside the selected engagement namespace and using relative paths for artifacts, but says nothing about what is destroyed or the cost/time of a darkside attack.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with purpose and followed by the execution-context caveat. No filler, no repetition of the title or schema.

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 values need not be described, but for a wrapper-style tool with a free-form 'arguments' array at 0% schema coverage the definition is under-specified. An agent still cannot determine what flag strings to populate or how stdin interacts with them.

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 carry the load. It only implicitly touches working_directory and engagement_id ('relative paths for engagement artifacts'); the central 'arguments' array of raw CLI flags and the 'stdin' parameter are entirely unexplained, leaving the agent to guess the required flag syntax.

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 ('Recover MIFARE Classic keys') plus the concrete technique ('darkside attack'), which is far more informative than the opaque tool name oc_mfcuk. It does not contrast itself with any sibling (e.g. other MIFARE/key-recovery tooling), so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit triggering condition: use it 'when nested auth fails', which tells the agent when this attack is the right choice. It stops short of naming an alternative tool for the non-failing case or stating preconditions such as required hardware/proximity.

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