action. For card_details and transaction asks, approval completes the follow-up action right there; for cross_app:* asks, approval records the user’s consent and the requesting app completes the action from its side. Never approve or deny on the agent’s own initiative: an approval is the user’s consent.
Personal sessions only. Approvals are a personal-consent surface, so sessions connected through a company get a clear not-available message instead of the inbox (
status: "personal_surface_only").Parameters
This tool takes no parameters.Returns
The pending, unexpired approvals newest first, each withid (pass it as approval_id to approve_request), action and a human actionLabel, appName (the app or company asking, when known), card (the card the ask is about, including the attached card behind it for attached-card mints; null for card-creation asks), params and a short summary (like "$25.00 card"), createdAt, and expiresAt, plus a count. Resolved, consumed, and expired requests never appear.