Agent Control Tower ACT

Live sandbox · fictional data

Watch AI agents get governed, live

Fictional agents call a fictional ERP through a real Agentgateway. Agent Control Tower decides every call, holds risky changes until a person approves them, and signs a tamper-evident record. Run a scenario, then follow it through the timeline, the approval inbox, and the evidence.

Run a scenario

Allowed FIN-READ-001

Read an invoice

The Invoice Agent reads invoice INV-1001 for an employee the read policy allows.

invoice-agent for employee-demo-42

Denied No grant

Open another client's documents

The same agent asks for client B's documents, which no grant covers. The gateway hides the tool and refuses the call.

invoice-agent for employee-demo-42

Denied FIN-WRITE-007

Change an invoice without a grant

The Invoice Agent tries to change INV-1001's total. Its write grant is observe-only, so the gateway refuses and the invoice stays as it was.

invoice-agent for employee-demo-42

Held, then approved FIN-WRITE-007

Correct an invoice, approved

The Payables Agent corrects INV-1002. The gateway holds the call until the demo controller approves it, then runs it exactly as requested.

payables-agent for employee-demo-finance

Held, then denied FIN-WRITE-007

Correct an invoice, denied

The Payables Agent asks to set INV-1003 to a total that does not match the order. The demo controller denies it, so the call never runs.

payables-agent for employee-demo-finance

Each visitor can run 12 scenarios an hour, one at a time. Nothing here can change the registry or policies, approve a call, or sign evidence: the demo controller decides held calls, and ACT signs on its own schedule.

Recent runs

Explore what was recorded

ExecutionsEvery run's timeline: each gateway decision, approval, and its place in the hash chain. Approval inboxHeld calls waiting for the demo controller, and what was decided. PoliciesThe rules and grants the gateway enforces, with the published revision. EvidenceSigned checkpoints of the audit chain and the key to verify them offline.

Enforcement covers calls routed through the gateway. A tool reachable another way bypasses these policies, which is why the lab's ERP accepts connections from the gateway only.