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

Skip to content
Gaten

Use case library

One approach, any use case.

For each agent use case: what Gaten checks, and a sample rule. These are examples — rules can be written for any action an agent can take.

Refunds & credits

A support agent can issue refunds to customers.

What Gaten enforces

Check each refund before it runs: auto-allow small ones, hold mid-size ones for finance, deny the rest.

Sample rule · illustrative

allow            when amount <= 100
require_approval when amount <= 1000  approver = "finance-lead"
deny             otherwise

Payments & payouts

An agent pays supplier invoices.

What Gaten enforces

Enforce daily limits per supplier and currency, and require two approvers above a set amount.

Sample rule · illustrative

allow            when vendor in approved_vendors and amount <= daily_limit
require_approval when amount > daily_limit  approvers = 2
deny             otherwise

Customer data access

An assistant looks up customer records to answer questions.

What Gaten enforces

Allow lookups only for the customer in the conversation; deny bulk exports.

Sample rule · illustrative

allow when customer_id == conversation.customer_id
deny  when rows > 1  reason = "bulk export not allowed"

Outbound messages

An agent emails customers on your behalf.

What Gaten enforces

Hold emails that mention pricing, legal terms or account closure for human review.

Sample rule · illustrative

require_approval when topic in ["pricing", "legal", "closure"]  approver = "support-lead"
allow            otherwise

Infrastructure actions

An operations agent manages cloud services.

What Gaten enforces

Allow restarts, require approval to change production config, deny deletions.

Sample rule · illustrative

allow            when action == "restart"
require_approval when env == "production"  approver = "on-call"
deny             when action == "delete"

Account changes

An agent changes plans, roles or passwords for users.

What Gaten enforces

Require a verified identity before any change, and approval for admin role grants.

Sample rule · illustrative

deny             when not user.verified
require_approval when role == "admin"  approver = "security"
allow            otherwise
Conceptual black gateway with a blue sphere passing through
Many actions. Your rules.Conceptual illustration

Have a different use case?

If an agent can do it through a tool, Gaten can put a rule in front of it. Talk to an expert about yours.