Loading Gatelion
Skip to content
GatelionBetaStart free

AI agents no longer just answer. They act.

Every action they take passes through your gate.

Orders placed, refunds issued, customer records changed. Gatelion checks each action against your rules before it reaches your systems. It runs at once, waits for a person to approve the exact values, or never happens at all. Every step goes into a record that can't be altered without it showing.

Start free Try a call

Free to use. No credit card. Works with MCP clients such as Claude Code.

One call, end to end

  1. Agent

    request

    purchasing-agent calls erp.purchase_orders.create

    supplier_id SUP-003 · max_total 1500.00 · for Rana

  2. Policy

    needs approval

    Rule po-large matches: max_total > 1000

    Held for approval. Nothing has reached the ERP.

  3. Approval

    approved

    Karim approves these exact values

    Bound to fingerprint 9f2c…e41a. Rana and the agent's owner can't approve.

  4. Re-check

    granted

    Policy, tool and agent checked again

    Unchanged, so the Gateway gets a signed grant valid for 60 seconds.

  5. Run

    succeeded

    Sent to the ERP once

    Purchase order PO-000042 created.

  6. Audit

    chain intact

    Every step recorded

    Chained by hash, so no event can be changed, removed or reordered unnoticed.

MCP · Streamable HTTPClaude CodeOpenAPI 3.0 & 3.1Postman collectionscurl commandsHosted GatewayWindows & Linux GatewaysHTTPS with your certificateCompany login (OpenID Connect)Passkeys & authenticator appsHash-chained audit trailCustomer sign-in for outside agents

How it works

From sign-up to a governed agent, in four steps.

In the console, a getting-started guide walks you through them and ticks each one off. Follow the quick start with a public test API.

  1. 01

    Connect a system

    Import its OpenAPI description. No description? Describe its operations, or start from a Postman collection or a curl command.

    curl -X POST https://api…/orders

  2. 02

    Choose the tools

    Each operation becomes a tool with a strict input schema. Agents get nothing you haven't added.

    erp.purchase_orders.create

  3. 03

    Write the policy

    Allow, require approval, or deny, per tool and agent, with conditions on the values. Try a call before you save.

    max_total > 1000 → approval

  4. 04

    Connect your agents

    Over MCP, with an agent token and the person it acts for. It only sees the tools the policy could let it use.

    claude mcp add gatelion …

The policy

Three outcomes. Your rules decide.

Rules are checked from top to bottom, and the first that matches decides: allow, needs approval or deny. Anything no rule allows is refused. The same call always gets the same answer, so no model is guessing whether it's safe.

Build rules in a visual editor or as JSON, with conditions on the values, such as an amount. In the console, Try it shows which rule decides a call before you save.

Pick a call, or watch them play.

tools/call erp.purchase_orders.create {"supplier_id":"SUP-003","max_total":"1500.00"}
  1. 1. readsinventory.list, purchase_orders.getAllow
  2. 2. cancelpurchase_orders.cancelDeny
  3. 3. po-largepurchase_orders.create, max_total > 1000Needs approval
  4. 4. popurchase_orders.createAllow
  5. OtherwiseDeny

Needs approval · Rule po-large. Waits for a person to approve these exact values.

The Gateway

It runs where your systems are.

The Gateway enforces your policy from its own signed copy of your configuration. Run it in our cloud, or install it next to your internal systems.

GATELION CLOUDYOUR NETWORK✕ no inbound connectionsagents call over MCPsecrets stay here↑ audit · ↓ signed configClaude CodeMCP clientYour own agentagent tokenA customer's assistantcustomer sign-inERPCRMPaymentsControl Planerules · approvals · auditGatewaychecks every call✓ allow⏸ needs approval✕ deny✕
  • A Windows or Linux service, set up by one installer script.
  • It only connects out to Gatelion. Nothing needs to reach in.
  • Your systems' secrets stay on that machine. Gatelion only knows their names.
  • Agents connect over HTTPS with your own certificate.

Agents connect to

https://gateway.corp.example:5200/mcp

If a Gateway loses contact with Gatelion, it keeps deciding from its last signed configuration for a limited time, then stops writes, then reads. It fails closed rather than act on rules that may have changed.

Who the agents are

Your team's agents. And your customers'.

Your own agents

Assistants and automations your team runs. Each has its own token and a list of people it may act for. Approvals go to a colleague: whoever owns the agent, issued its token or asked for the action can't approve it.

Approvals

1 waiting

erp.purchase_orders.create · for Rana

Supplier
SUP-003
Lines
2 × SENSOR-007
Max total
1,500.00
Rule
po-large · policy v3
Approve this operationReject

Your customers' agents

Customers bring their own AI assistant. It signs in with your existing customer login, and the customer sees what it may do before allowing it. They can confirm important actions themselves and withdraw the permission at any time. Your system gets a signed header saying which customer each call is for.

Signed in as dana@example.com

Travel Assistant wants to act for you

It will be able to use:

  • Search flightsruns at once
  • Book a flightyou confirm each one
AllowCancel

You can withdraw this permission at any time.

Put a gate in front of your agents.

Sign up, connect a system and govern your first agent call today. Every action after that passes through your rules.

Start free Read the docs
  • Free to use
  • No credit card
  • Hosted or in your network