CyberChef MCP Server

cyberchef_recipe_execute

Destructive

Run a saved recipe by UUID with input data to process it according to the recipe's operations.

Instructions

Execute a saved recipe with input data.

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": {
      "id": "<id>",
      "input": "<input>"
    },
    "name": "cyberchef_recipe_execute"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Recipe UUID
`input`	Yes	Input data to process

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0Sep 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false, and the description adds no behavioral context beyond them. It does not disclose side effects, whether input is irreversibly transformed, quota consumption, or what 'execute' entails — all relevant given the destructive flag. There is no contradiction with the annotations, but the description contributes no additional transparency.

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?

The description is a single eight-word sentence with the verb front-loaded and zero filler words. It is efficient and scannable, though slightly under-sized for a tool carrying a destructive flag and a near-identical sibling.

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?

There is no output schema, so the description should convey what the call returns on success, but it is silent on that. With destructiveHint=true and a large sibling set that includes cyberchef_bake and cyberchef_recipe_test, the description is too thin for an agent to invoke it confidently without external knowledge.

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 coverage is 100%: the schema already documents 'id' as 'Recipe UUID' and 'input' as 'Input data to process'. The description's phrase 'with input data' merely restates the schema, so it adds no parameter-level meaning; the high-coverage baseline of 3 applies.

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 (Execute) and resource (a saved recipe) along with the input payload, making the core action unambiguous. The qualifier 'saved' distinguishes it from recipe-management siblings like cyberchef_recipe_create/get/delete, but it does not explicitly differentiate it from the close sibling cyberchef_bake, so the distinction is implied rather than stated.

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?

The description gives no when-to-use guidance, exclusions, or mention of alternatives. An agent cannot tell from this text whether to choose cyberchef_recipe_execute or cyberchef_bake (or cyberchef_recipe_test), since the selection criteria between saved-recipe execution and inline baking are never stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.