Every AI action, through the gate.
Each action your agents propose is allowed, sent to a named person for approval, or refused — before it runs. Every decision on record.
Every action starts as a request.
A registered agent asks to use one of its declared tools, on behalf of a named person. Nothing has run yet.
tool send_payment
for finance@acme.example
One of three outcomes, before it runs.
AllowRead-only actions and those your rules allow go straight through.
Hold for approvalActions that change something wait for a named person.
RefuseUndeclared tools are refused. The reason goes back to the agent.
Every decision, written down.
Allowed, held, refused — with the agent, the tool and the person it acted for.
Drag an action into the gate. Watch it decide.
These are TaskGate's default rules: read-only actions pass, anything that changes something waits for its approver, and tools an agent never declared are refused. Tap a card on a phone.
Every decision you make here lands in this log.
One console. Every agent, every decision.
Register agents, clear the approvals queue, read the decision log and measure each agent — signed in with your company identity. Every decision you make at the gate above lands in its log.
Decision log
today| Time | Agent | Tool | Acting for | Decision |
|---|---|---|---|---|
| 14:02 | invoice-agent | send_payment | finance@acme | Held |
| 14:01 | invoice-agent | read_invoice | finance@acme | Allowed |
| 13:47 | support-agent | delete_customer | ops@acme | Refused |
| 13:40 | support-agent | search_tickets | ops@acme | Allowed |
| 13:22 | crm-agent | update_contact | sales@acme | Approved |
Agent registry
4 agents| Agent | Owner | Purpose | Declared tools |
|---|---|---|---|
| invoice-agent | Finance lead | Pays approved invoices | read_invoice · send_payment |
| support-agent | Support lead | Answers customer tickets | search_tickets · reply |
| crm-agent | Sales lead | Keeps contacts current | update_contact |
| research-agent | Ops lead | Finds internal answers | search_docs |
Approvals
waiting for a personinvoice-agent wants to send_payment
Acting for finance@acme · €4,200.00 · held because it moves money. Approve and it executes.
crm-agent wants to update_contact
Acting for sales@acme · held because it changes a record.
Evaluations
per agentAgent registry
Every agent carries an owner, a purpose and the tools it declared. Undeclared means refused.
Approvals queue
Held actions wait for the named approver. Once approved, they execute.
Decision log
Every allow, hold and refusal is recorded, with the agent and the person it acted for.
Evaluations
Each agent's performance is measured, so you know which ones earn more room.
Guardrails on every run
Capped tool calls per turn, timeouts and session expiry. New capabilities arrive as modules under the same gate.
One gate for all your agents. Set up for your team.
Sign up with your work email and we set up your workspace, your policy and your first agents with you.
Sign up- The gate on every agent action
- Agent registry and default-safe policy
- Approvals queue with named approvers
- Full decision log
- Evaluations per agent
- Company sign-in and per-user workspaces
Put your agents through the gate.
Leave your work email. We'll take it from there.