Fetch Hive

Make a new webhook secret

rotate_webhook_secret

Destructive

Replace the webhook secret of an agent or a deployed workflow, for example after it leaked. The old secret stops working at once, so call without approved first, tell the person, and call again with approved: true. The new secret is never shown here: the person copies it from Get code on the dashboard_url. Never ask them to paste it into the chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rotate_webhook_secret"
  }
}

Input Schema

Name	Required	Description
`agent_id`	No
`approved`	No	true only after the person has agreed.
`workflow_id`	No	A deployed workflow (or pass agent_id).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the supplied destructive/non-idempotent annotations, it discloses the critical consequence that 'the old secret stops working at once' and that the new value is never returned by this tool, only retrievable by the person via Get code on dashboard_url. That is exactly the operational context the annotations cannot convey.

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?

Four short sentences, each carrying distinct information: what it does, the immediate invalidation, the approval sequence, and where the secret comes from. The most consequential facts (old secret dies immediately) are front-loaded after the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description explicitly covers the return behavior (secret not shown, retrieved elsewhere), the safety consequence, and the human-approval protocol. Nothing an agent needs in order to call this destructive tool safely is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the meaning and sequencing of 'approved' (a human-consent gate requiring two calls) and covers the agent/workflow target choice, complementing the 67% schema coverage. 'agent_id' itself is not described in the schema, but 'of an agent or a deployed workflow' supplies its intent indirectly.

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

Purpose5/5

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

States a specific verb and resource ('Replace the webhook secret') and scopes it to two target types, 'an agent or a deployed workflow'. The use case ('for example after it leaked') further pins down intent so an agent can distinguish this from unrelated rotation or config tools.

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

Usage Guidelines5/5

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

Gives an explicit two-step procedure: call first without 'approved', tell the person, then call again with approved: true. It also names the triggering situation (a leaked secret) and forbids a specific misuse (asking the person to paste the secret into chat).

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

All Fetch Hive tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?