A question companies ask

The question: We want AI agents to act on our ERP and other systems. How do we stop one from doing something it should not?

How to run AI agents on company systems, safely

Give each agent its own identity and its own limits, and check every action as it happens. On Substrait, an agent can never do more than its owner may, every action is recorded as the agent acting for a named person, and the agent's identity can be switched off at once.

Last updated

Why this is hard

An app does the same thing every time it runs. An agent is given a goal and a set of tools, and decides at runtime what to call, in what order. A review at go-live cannot know everything an agent will do. An agent that reads an email or a supplier’s document can also be told, by that content, to do something else.

What Substrait does

An agent is a tool its builder owns. It is registered, deployed and governed like any other tool on Substrait.

Its own identity, never borrowed. Each agent gets an identity that Substrait issues, scopes and can revoke. It never acts on a person’s standing credentials.

Narrower than its owner. An agent’s authority is the smaller of two things: what its owner may reach, and what the agent was granted. Everything else is denied.

A check on every action. Substrait checks each action against the agent’s limits at the moment it happens. Calls to company data go through Substrait’s gateway, under the agent’s own grant.

A record of who it acted for. Every action is recorded as “this agent, acting for this person”. One accountable person stands behind every action.

A switch on the identity. Switching off an agent’s identity stops it at once, wherever it runs.

People decide what agents should not. When an agent needs a human decision, it asks through Substrait’s communications centre, and the right person answers from their own channel.

Questions and answers

Why is an agent riskier than an app?

An app does the same thing every run, so its reach is known before it goes live. An agent decides at runtime which tools to call, and content it reads, such as an email or a document, can try to redirect it. That is why Substrait checks an agent's actions as they happen, not only at go-live.

Does an agent use the owner's own credentials?

No. On Substrait each agent has its own identity, scoped and revocable. It never borrows the standing credentials of the person who owns it.

Does an agent need a seat?

No. On Substrait an agent is a tool its builder owns. It holds no seat.

Related

Start with a result, not a rollout.

Book a demo and bring one real use case. We will show you how a tool your people build goes live on Substrait, with its data approved and its security check passed.