Promoting a Policy to Enforce
A HYPR AgentPass™ policy in Observe mode changes nothing. It only records what it would have done. Promoting it to Enforce is when it starts to block requests, hold them for approval, or cut a model's reply short, for every agent and user in its scope. This page covers the check before promotion, the step itself, and the way back.
Promoting a policy is an administrator task. Changing a policy's mode needs the Edit permission on Policies. Where that permission is limited to your own records, you can change only the policies you own: those whose Supervisor Email is yours.
Check Before You Promote
Open the connector's Decisions card: go to Connectors, open the connector, and click the Policies tab. Set the Policy filter to the rule you are about to promote, then work through these checks.
| Check | How | Why it matters |
|---|---|---|
| It catches what you meant | Would block rows appear for the traffic the rule is about. Open a few, and read Why it matched | A rule with no Observe matches does nothing once enforced, either |
| It catches nothing else | Scan the Agent › Tool column, or filter by tool, for calls you did not mean to stop. For traffic that happens only weekly, widen the window to 7 days | Every one of those rows becomes a blocked or held request on promotion |
| Its message reads well | Read the policy's message as the person who will receive it | A blocked agent or user sees the policy's name and this message, never the condition |
| It wins where it should | Look for another enforcing rule that blocks or holds the same traffic at a lower priority number | The first enforcing block or hold decides, so only its message is shown |
| Someone can approve | For REQUIRE_APPROVAL, confirm the agents in scope have a supervisor | A request from a service agent has no one to approve it, and does not complete |
For a draft written with AI, the wizard's Run backtest replays it against the last seven days of this connector's traffic before you save. See Backtest against last 7 days.
A rule that judges a model's reply ends that reply with a short note when it matches. On a Microsoft 365 Copilot connector, the user sees a blocked notice instead of the answer. Scope such a rule to the connector you mean before you promote it. See What a Match Does, by Kind of Traffic.
Promote
- Open Oversight → Policies, or the connector's Policies tab.
- On the policy's row, open the Mode dropdown, and choose
ENFORCE. - In the Change mode of policy "…"? dialog, click Set ENFORCE.
The policy's action applies from then on, and a Policy "…" set to ENFORCE message confirms the change. Promotion changes only whether the action is applied, not the rule itself.
The Mode dropdown lists each mode with a short description, and marks the current one (current).
| Mode | Description in the menu |
|---|---|
DISABLED | Skipped at evaluation; no logging, no enforcement. |
OBSERVE | Logs matches as "would-have-denied" events; traffic flows. |
ENFORCE | Active — blocks or requires approval on matching requests. |
The confirmation dialog shows the mode you are leaving, the one you are moving to and its description. When you move to ENFORCE, it adds a tip: Tip: confirm the OBSERVE-mode events look right before promoting, or run a backtest from the policy's wizard. The confirm button names the new mode, such as Set OBSERVE.
A REQUIRE_APPROVAL policy whose condition reads inference.* cannot be promoted. The gateway refuses the change, and asks you to use DENY to block, or to keep the policy in OBSERVE to record where approval would have been required. See Where Require Approval Applies.
Watch the First Hour
On the Decisions card, set the window to Last hour, and Mode to ENFORCE. Where you used to see Would block, the rule now records Blocked or Approval.
An unexpected spike, or blocks on a tool you did not mean to reach, is the signal to roll back and narrow the rule. When someone reports that an agent was stopped, start from When a User Reports a Block.
Roll Back
The same Mode dropdown takes a policy back at any time.
| Choose | Effect |
|---|---|
OBSERVE | The action stops applying. Matches are still recorded as Would block, so you can keep tuning the rule against live traffic |
DISABLED | The policy is not evaluated at all. Nothing is enforced or recorded |
Rolling back is a safer first move than editing the condition under pressure. Demote the policy, narrow the rule while it observes, then promote it again.
If the problem is a condition you changed, click Restore on the connector's Policies tab. It appears on any policy whose expression has changed since it was created. In the Restore previous CEL on "…"? dialog, check the expression it shows, and click Restore. The current and previous expressions swap, so restoring again undoes the restore.
Related
- How Policies Are Evaluated — modes, actions, priority and what a match does
- Investigating a Policy Decision — the Decisions card and the decision panel
- Redundant and Conflicting Rules — enforcing rules that stop another rule from ever running
- Approving and Denying Agent Actions — what a supervisor sees when a rule holds a request