Learn · Guides
Run an agent on a leash
Give an AI helper a job, a short list of tools, and a person to sign off.
Checked against the product on · written for people writing code
An agent reads what it is given, proposes an action, and stops. What it can reach is set by the connectors you bind to it. With no connectors bound, it reaches nothing.
Automate
New agent
- Name
- Ticket triage
- What it does
- Read an inbound ticket and propose a queue and a priority.
- May reach
- ticket-apiConnectors. Anything unlisted is unreachable.
- Ask a person before acting
- Yes
Open Agents, select New agent, and write the job in one or two sentences.1
The text is the instruction the agent runs on. Plain language works.
Bind the connectors it needs, then select Dry run.2
A dry run proposes without dispatching. Read the proposal before you create the agent.
Watch it work
Automate
Agents
| Agent | Job | May reach | Sign-off | State |
|---|---|---|---|---|
| Ticket triage | Sort inbound tickets | ticket-api | Required | Running |
| Plant watch | Summarise excursions | plant-otel | Required | Running |
| Doc drafter | Draft change notes | none | Not needed | Paused |
Open Agents and confirm the state reads Running.1
Read the May reach column.2
This is the full set of hosts the agent can send a request to.
Read the default-deny line.3
What holds the leash
| Guard | What it does | Where it runs |
|---|---|---|
| The envelope | Narrows a step to the tools its node names, within the grant the agent holds. | At the call site, on every tool call. |
| The egress check | Derives the reachable hosts from the bound connectors and checks every outbound call. | Before DNS on the first request, and again on every redirect. |
| The review gate | Holds a sensitive action for a person. | On the proposal, before dispatch. |
| The logbook | Writes the step, the proposal, the decision, and the outcome. | On every step. |