request_approval
Create an approval request that forces human authorization before dangerous operations such as deletions or transfers. The account owner receives email notification for approval via dashboard or link.
Instructions
Create an approval request in the human approval gate (runtime control plane Phase 3; Pro+ only). Call it before dangerous operations (deletion / money transfer / account closure etc.); the account owner gets an email notification and a human approves or denies via the dashboard or the email link. Important: no MCP tool exists to approve or deny (an AI agent cannot self-approve its own request). Poll the result with get_approval. Expiry after timeoutSeconds (default 3600) counts as denied. Server-side consumption: passing approvalId to a dangerous mutation tool (bulk_delete_calls / purge_expired_plaintext / retry_failed_webhook / auto_silence_noisy_alert / extend_customer_trial / apply_promo_code_to_customer) makes the backend verify action match + approved + within expiry + unconsumed, and consume it on execution (1 approval = 1 execution). In that case create the request with an action exactly matching the target tool name. Example phrasing: "deleting user usr_123 is a dangerous operation — get human approval first"
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Operation identifier (1-128 chars; alphanumerics, ._:-, and spaces). E.g. delete_user | |
| summary | Yes | One-line human-readable description (1-500 chars; appears verbatim in the approval email) | |
| metadata | No | Supplementary JSON object (up to 4KB, optional) | |
| timeoutSeconds | No | Approval deadline in seconds (60-86400, default 3600) |