Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Require a Person for High-Value Agent Actions

Purpose​

This playbook gives the running order for letting agents make routine calls on their own, while HYPR AgentPass™ holds named sensitive actions. A held action waits until a person approves it with a passkey.

Each step is a summary. The detail, with screenshots, field values and caveats, is on the page the step links to.

When you finish:

  • The actions you chose are held until a supervisor approves them.
  • Each approval is bound to that person and that action.
  • The policy set stays readable as it grows.

Architecture​

A policy evaluates each request as it passes through the gateway. A Require approval match holds the request, and asks the supervisor on their phone. For the diagram and the request path, see Architecture: The Request Path.

Prerequisites​

You need the following:

  • At least one connector carrying agent traffic
  • Supervisors with an approval passkey
  • A drafting model, if you want to draft policies with AI

For the full list, see Prerequisites.

Procedure​

Complete these tasks in order.

Find What Is Ungoverned​

Open Policies → Coverage. The table shows which connector and tool pairs a rule reaches, and which no rule reaches. Pick the sensitive actions from the ungoverned rows.

See Policy Coverage.

Draft the Rule in Observe Mode​

Write the rule with the action Require approval, and leave it in Observe mode. Write it by hand from Add Policy, or from a plain-English goal with Author with AI. In Observe mode, the rule records what it would have held, without holding anything.

See Writing a Policy by Hand, Authoring a Policy with AI and Setting Up AI Authoring.

Check the Impact and the Overlap​

Read the rule's plain-language summary and its match history. Then open Policies → Redundancy, and confirm no existing rule already covers the same traffic or sits ahead of yours.

See Understanding Your Policies and Redundant and Conflicting Rules.

Promote the Rule to Enforce Mode​

Change the rule's mode from Observe to Enforce. From the next matching request, the action is held until its supervisor answers.

See How Policies Are Evaluated and Observe First, Then Enforce.

Require Signed Approvals​

Open Advanced → Gateway Settings → Passkeys (FIDO2). Set the passkey approval policy, and set Require signed approvals to Required (production). Each approval is then bound to the supervisor's passkey, and to the action approved.

See Connecting to Your HYPR Tenant.

Keep the Policy Set Healthy​

Review Policies → Suggested for rules the gateway proposes from observed traffic. Attach evaluator agents to sessions, so suspicious behavior is surfaced without blocking.

See Suggested Policies and Session Watch: Evaluator Agents.

Validate​

Have an agent attempt one of the chosen actions, and check the following:

  • The request is held, and the supervisor's phone shows the approval.
  • Approve (Allow on iPhone) releases the action, and Deny stops it.
  • The rule's match count on Policies → Rules increases.

See Approving and Denying Agent Actions.

Logs and Audit Trail​

Every held request and its outcome is on the console's Approvals page. The request itself, with the policy that held it, is in the Request Log.

See Approvals in the Console and Reading Your Request Log.