Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

Revoke Delegated Subagent Key

x402_revoke_delegate_key
DestructiveIdempotent

Permanently revoke one delegated subagent spend key by delegate_id (sbd_*), or revoke every active delegated key across the account when revoke_all=true. Use this immediately to disable a compromised, retired, or runaway subagent; do not use this for a temporary reversible pause across the whole account (use x402_set_account_freeze) or to adjust caps (use x402_update_delegate_key). Destructive and irreversible: revoked keys immediately fail with HTTP 401 and cannot be reactivated. Requires a master sbk_* spend key; provide either delegate_id (single key) or revoke_all=true (entire swarm).

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": "x402_revoke_delegate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional audit-log reason for revocation (e.g. "key_rotated" or "compromised_worker").
spend_keyNoMaster Stripe account spend key (format: sbk_<43+ chars>). Delegated subagent keys are rejected with HTTP 403. Optional if supplied via the x-atlas-spend-key HTTP header.
revoke_allNoSet true to execute the emergency swarm kill switch revoking EVERY active delegated subagent key on the account (omit delegate_id when true).
delegate_idNoUnique delegated subagent key identifier returned by x402_issue_delegate_key or x402_get_account (format: sbd_<16 hex chars>, e.g. sbd_1122334455667788).

Output Schema

NameRequiredDescriptionDefault
okYesTrue when revocation succeeded.
revokedNoTrue when a single delegated key was revoked.
revoked_countNoNumber of delegated keys revoked when revoke_all=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real consequence detail the annotations cannot: revoked keys fail with HTTP 401 and cannot be reactivated, and a master sbk_* key is required. It does not explain what happens on repeated revocation despite idempotentHint=true, so it stops short of a 5.

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?

Three sentences, front-loaded with the action and scope, then usage, then consequences. Slight redundancy with the schema on key prefixes, but no filler sentences and nothing 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 destructive mutation with an output schema present, the description supplies the authorization requirement, the blast radius of revoke_all, the irreversibility, and the routing to alternatives. Nothing an agent needs to invoke it safely is missing.

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%, so the parameter formats and constraints are already documented in structured fields. The description reinforces the either/or selection between delegate_id and revoke_all=true but adds no syntax or behavioral detail beyond the schema's own text. Baseline 3 is appropriate.

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 ("Permanently revoke one delegated subagent spend key") plus the bulk variant, and immediately distinguishes itself from siblings that pause or adjust keys. An agent can tell exactly what this does without opening the schema.

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 trigger ("Use this immediately to disable a compromised, retired, or runaway subagent") and explicit exclusions naming the correct alternatives: x402_set_account_freeze for a reversible pause and x402_update_delegate_key for cap changes. Both the when and the when-not are present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources