Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Rotate webhook secret

tailscale_rotate_webhook_secret

Rotate a webhook secret to invalidate the old value and receive a new one once; save it immediately because it cannot be retrieved again.

Instructions

Rotate a webhook's secret. Returns the new secret -- save it immediately, as it cannot be retrieved again. The old secret is immediately invalidated.

SECURITY: the response body contains the secret verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive.

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": {
      "webhookId": "<webhookId>"
    },
    "name": "tailscale_rotate_webhook_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe webhook ID whose secret to rotate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / webhookId / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

A4.2/5.0
Behavior5/5

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

Annotations cover the safety profile at a shallow level (readOnlyHint=false, destructiveHint=false, idempotentHint=false), but the description adds genuinely new behavioral facts: the new secret is returned once and cannot be retrieved again, and the old secret is invalidated immediately. The explicit security note that responses may be persisted in logs and transcripts is exactly the kind of context an agent cannot infer from structured fields.

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 most important operational fact (save the secret immediately, it cannot be retrieved again) is front-loaded, and the security warning is set off cleanly. There is minor redundancy between 'save it immediately' and 'cannot be retrieved again', which keeps it from being maximally tight.

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 carries the burden of explaining the return value and does so precisely: the response body contains the new secret verbatim, once. Combined with the invalidation semantics and the sensitivity warning, an agent has everything needed to call this tool and handle its result correctly.

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?

There is a single required parameter whose schema description already fully covers its meaning ('The webhook ID whose secret to rotate'), so the baseline is 3. The description adds nothing about the parameter beyond the schema, but nothing is missing either.

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?

The description states a specific verb and resource ('Rotate a webhook's secret'), which an agent can immediately distinguish from siblings such as tailscale_get_webhook, tailscale_update_webhook, tailscale_test_webhook, and tailscale_delete_webhook. No ambiguity about what operation is performed.

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?

Usage is implied rather than stated: the invalidation and one-time-reveal semantics hint at when the tool is appropriate, but there is no explicit when-to-use guidance, no mention of prerequisites (webhook must exist, current secret in use will break), and no routing away from alternatives like tailscale_update_webhook.

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