Activate or Disable a Pakt
Stage lifecycle changes through MCP and leave the human approval ceremony in the dashboard.
The MCP tool creates a browser approval request. The owner completes that request with the account's enrolled, backed-up passkey. An agent can request a review, but it cannot approve itself or a Pakt.
MCP Prepares; the Owner Approves
The MCP call only prepares a browser review. The root becomes active or disabled only after the owner approves the exact change with the enrolled passkey.
Activate
Ask the connected agent:
Stage the Pakt we just reviewed for activation. Do not claim it is active.
Give me the dashboard approval step.The agent calls prepare_pakt_activation with the exact canonical SSZ returned
by draft_pakt. Pakt creates a random five-minute challenge bound to the
authenticated account, deployment environment, and canonical root.
The owner then opens the Pakt dashboard, checks the exact account, environment, root, and ALLOWED / NOT ALLOWED summary, and approves with the enrolled passkey. The browser ceremony—not the MCP response—activates the root.
Confirm the result with list_pakts or get_execution_context before treating
the root as available to an action agent.
Disable
Ask the connected agent:
Stage terminal disable of Pakt root <root>. Do not disable any other root.The agent calls prepare_pakt_disable with that exact active root. The owner
reviews the separate disable ceremony in the dashboard and approves it with the
same passkey. Disable is terminal for that account/root binding.
Authority Held Outside MCP
The owner retains the passkey and wallet or venue-master keys. The secure boundary retains the approval and receipt credential keys, and the wallet provider retains the execution signing key. MCP carries review challenges, status, receipts, and authorized signed requests between those boundaries.
Passkey enrollment, wallet connection, and recovery belong to Get started, not to an agent-run guide.