Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

Set Account Emergency Freeze

x402_set_account_freeze
DestructiveIdempotent

Emergency kill switch that immediately freezes (frozen=true) or unfreezes (frozen=false) all capability spends across the master account and every delegated subagent key. Use this to pause all spending immediately during an incident while preserving keys for later resumption; do not use this to permanently destroy individual subagent keys (use x402_revoke_delegate_key). High-impact and reversible: while frozen, every spend attempt fails closed with HTTP 403 account_frozen. Requires a master sbk_* spend key (delegated keys receive HTTP 403).

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": {
      "frozen": "<frozen>"
    },
    "name": "x402_set_account_freeze"
  }
}

Input Schema

NameRequiredDescriptionDefault
frozenYesSet true to immediately halt all master and subagent spends across the account, or false to lift the freeze and resume spending.
reasonNoOptional incident or operator audit reason recorded on the account freeze state (e.g. "anomaly_investigation").
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.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the account freeze state was updated.
frozenNoActive emergency freeze flag after this operation.
account_idNo
frozen_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses reversibility and state preservation, the exact failure mode of affected spends ('fails closed with HTTP 403 account_frozen'), and the authorization requirement (master sbk_* key; delegated keys get HTTP 403). The 'reversible while destructiveHint=true' framing is complementary rather than contradictory: the halt is disruptive to spending but the keys survive.

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 lead phrase 'Emergency kill switch' front-loads the nature and stakes of the tool, and the when-not-to-use clause follows immediately. It is only slightly redundant in re-explaining frozen=true/false, which the schema already covers.

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?

An output schema exists, so return values need not be described. For a destructive, account-wide mutation, the description supplies impact scope, reversibility, failure behavior, and auth requirements — everything an agent needs to invoke it safely.

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 description coverage is 100%, so frozen, reason, and spend_key are already fully documented in the schema, including format patterns and header fallback. The description restates the frozen=true/false semantics and adds the account-wide blast radius, but contributes no new syntax or format detail. Baseline 3 applies when the schema carries the parameter burden.

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 action ('freezes or unfreezes all capability spends') with explicit scope: master account plus every delegated subagent key. It also names the sibling it must not be confused with (x402_revoke_delegate_key), so an agent can route correctly without opening either 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 when-to-use ('pause all spending immediately during an incident while preserving keys for later resumption') and an explicit when-not-to-use with the named alternative ('do not use this to permanently destroy individual subagent keys (use x402_revoke_delegate_key)'). It also states the prerequisite that delegated keys are rejected, which the agent needs before calling.

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