How protected MCP actions reach you for approval

A protected MCP operation prepares work for a person to review in Adapt. The connector cannot approve its own request.

1. The assistant calls the protected tool with exact parameters.
2. Adapt stores the request and returns an action reference and review link.
3. Open the link while signed in. Read the action, target, values, warnings and expiry.
4. Approve or cancel with a separate button. Opening the link alone does not approve.
5. Adapt rechecks permissions and the stored target before running the stored request through normal application checks.
6. The assistant can fetch the recorded result afterwards.

For example, if a workflow changed after publishing was prepared, the old review is rejected. Prepare a new one showing the current work.

Sending, publishing, campaign launch or resume, workflow restore and permanent file removal declare their review requirements in the tool contract. Ordinary management can run directly with separate management consent.

The boundary

• Requests belong to one account and workspace, expire and can be claimed once.
• Protected requests are bound to exact parameters and target revision.
• A key, delegated token or external assistant cannot be the human approver. A model's approved: true is not consent.
• Campaign content, sender and recipient checks still apply.

Waiting for review is not success. Read whether the action completed, failed or has an unconfirmed outcome. Inspect uncertain outcomes before retrying. Permanent file removal cannot be reversed by a record restore.

See MCP tool groups and capability discovery and MCP limits and actions that still need you.