Review approval-gated actions

Approval lifecycle

1. 1
   The agent requests an action

   The tools service validates the tool, connection, account, and input schema.

2. 2
   Kern creates one pending approval

   The tool returns an approval id instead of performing the side effect.

3. 3
   The operator reviews it

   Home shows the tool, action, account, and bounded payload for approval or denial.

4. 4
   Kern executes once

   Approval resumes the held action. The agent polls the original approval id; it must not re-issue the request.

5. 5
   The audit becomes terminal

   Success, failure, or denial is recorded in Tool audit.

What to review

• The connected account is the one you intend.
• Recipients, targets, quantities, and visibility match the request.
• The payload does not contain secrets or unrelated private data.
• A cross-tool workflow has not combined data in an unexpected way.
• The action is still timely; deny stale requests rather than approving them later.