Skip to main content
Glama

Rotate a domain's token signing key

rotate_domain_signing_key
Destructive

Rotate a domain's token-signing key to replace a compromised key while old tokens remain valid until expiry; then revoke client tokens. Requires confirm=true.

Instructions

Creates a new key for signing the domain's tokens. The previous key keeps verifying until the tokens it signed expire, so nothing valid is cut off. For a key believed stolen: rotate, then revoke each client's tokens. Requires confirm=true.

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": {
      "domainId": "<domainId>"
    },
    "name": "rotate_domain_signing_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to act. Omit/false returns a preview only.
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds genuinely useful behavior beyond destructiveHint=true: the previous key keeps verifying until its tokens expire, so no valid token is cut off, and the confirm/preview gate is restated. That grace-period semantics is the key fact an agent needs to predict the effect of a destructive operation, though return values and any propagation delay are unstated.

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?

Three tight sentences, front-loaded with what the tool creates, then the safety-relevant effect, then the incident procedure and the confirmation gate. Nothing is redundant or buried.

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?

For a two-parameter mutation with no output schema, the description covers effect, reversibility/grace behavior, the confirmation gate, and the theft-response workflow. An agent has what it needs to call this correctly and to know what to do next.

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% and both parameters (domainId source, confirm preview behavior) are already documented in the schema. The description's 'Requires confirm=true' restates the schema rather than adding meaning, so the baseline 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?

States a specific verb and resource: 'Creates a new key for signing the domain's tokens,' which separates it from the API-key and client-secret rotation siblings by naming the token-signing key explicitly. It never names a sibling outright, so the differentiation is inferred rather than declared.

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 a concrete scenario ('For a key believed stolen: rotate, then revoke each client's tokens'), effectively routing the agent to a follow-up revoke step. It does not say when a routine, non-compromise rotation is appropriate versus other rotation tools, leaving some inference.

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