Step 3: Operate

How should high-risk AI agent actions be approved?

Send every high-risk action to a named person before it runs. Low risk runs. Prohibited is blocked. Each decision is recorded.

  • Low risk runs
  • High risk waits
  • Prohibited blocked

Request early access

Interactive example

Who decides?

Pick an action and see what policy does.

An agent wants to

Policy decides

Pick an action

The record

  1. Nothing yet

Interactive example. Not the live product.

Who may approve

Three rules for approvers

A named person

Not a shared inbox

With the right role

Set in policy

Never your own request

Owners are the exception

In the product

The approval queue

The approval queue in MFDIO: pending actions with risk level, the action, the agent that proposed it and when it was requested.
Approvals in the current MFDIO interface. Sample data.
  • Every pending action
  • Risk level shown
  • Approve or decline

What an approver sees

  1. 1

    The action

    What the agent wants to do

  2. 2

    The context

    Why it wants to

  3. 3

    The decision

    Recorded with name and time

Status

Today Works now

  • Email, chat and record writes wait for approval
  • No self-approval unless you are the Owner
  • Per-organization emergency stop

Roadmap Planned

  • Enforcement on live actions in customer systems through built-in connections

Next: keep the evidence

Prove records who decided and what it cost.

Go to Prove