Dry-run a new agent policy against past activity before it goes live. See how it works

Skip to content
Gaten

Runtime policy for AI agents

Every agent action, checked before it runs.

Decide what your AI agents can do alone, what needs a person, and what must never happen — enforced on every action.

Step 1 of 4 · Agent acts

Your AI agent tries to take a real action.

Support agent wants to refund $500

Your rules

Decide the limits.

Readable, versioned policy.

Runtime checkpoint

Check before acting.

Your rules, on every action.

Gaten
AllowApprovalDeny
Every decision, recorded.

How it works

A policy checkpoint between your agents and the real world.

Prompts are requests, not limits. Your rules are checked outside the model, at the moment an action happens.

  1. 01

    Intercept

    An agent calls a tool. The call reaches your policy before it reaches the real system.

  2. 02

    Evaluate

    Versioned rules check the action, its arguments, the agent and the context.

  3. 03

    Decide

    Allow it, deny it, or hold it for a named person to approve — in real time.

  4. 04

    Record

    Every request and decision is written to an audit trail, with the policy version used.

See a decision

Allow, deny, or ask a person.

The same refund agent, three amounts, three outcomes — each decided by a rule you wrote and recorded for audit.

A blue sphere passing through a policy checkpoint sculpture
Illustrative — sample data
Policy decision · liveIllustrative — sample data
  1. 1 · agent requests action

    support-agent → issue_refund()

    amount: $500 · order #A-2210

  2. 2 · evaluate policy refunds-policy v2.4

    match: $100 < refund.amount ≤ $1,000

  3. 3 · decisionRouted to finance leadREQUIRES APPROVAL
  4. 4 · recorded to audit trail

    decision_id dec_8f3a · 14:02:11 UTC

Platform

Built for agents running in production.

Rules for any action
Refunds, payments, data access, messages, infrastructure — if an agent can do it through a tool, you can write a rule for it.
→ Any use case
Human approval when it matters
Held actions reach the right approver with full context, timeouts and escalation.
→ Clear accountability
Dry-run before you publish
Test a new rule against past agent activity and see what it would have changed.
→ Safe rollout
A full audit trail
Every request, outcome, approver and policy version, in an append-only log.
→ Audit-ready

Example policy

Readable enough for finance. Precise enough for engineering.

policy "refunds" version "2.4" {
  action  = "issue_refund"

  allow            when amount <= 100
  require_approval when amount <= 1000  approver = "finance-lead"
  deny             otherwise            reason   = "exceeds agent authority"
}

Illustrative syntax

Conceptual black gateway with a blue sphere passing through
Your rules · every agent actionConceptual illustration

Every agent action, checked first.

From your first support bot to a fleet of autonomous agents, talk to an expert about putting your agents under policy with Gaten.