Glossary

Least privilege

Least privilege means an account holds only the access it needs for its task, and nothing more. For AI agents, Ares applies it per job and adds an expiry, so the access ends when the job does.

In a run

The credential is issued from two inputs: what your directory says the requesting person may do, and what the first agent needs. When the job ends or the time runs out, the credential stops working. No standing access is left behind.

Our word for it

The permission is for one job and narrows at each handoff.

Why standing access is the problem

An agent with a standing account keeps its access between jobs, and that access tends to grow. One wrong instruction can then reach everything the account was ever given. A credential that belongs to one job keeps a wrong step inside that job.

Across a chain of agents

When one agent hands work to another, the second agent gets the overlap of the caller’s permission and what it needs. It never holds more than the agent that called it. See delegation.

What you decide

You choose the directory groups that set what a person may hand to an agent, and the rules for each agent. Ares applies them on every call.

Where it stops

Least privilege is only as narrow as the rules you approve. If a rule gives an agent more than the job needs, Ares applies that rule as written. Revoking every credential of a job in one action is planned.

Run the sandbox and read what the credential for each job names.

Related terms

  • Scoped credentialA scoped credential covers a named set of actions for a limited time, instead of everything an account can do.
  • DelegationDelegation is one party handing a task, and part of its authority, to another.

Tell us about one workflow.

We will say whether an agent should do it, and what the first step costs.

A senior member of the team replies within two business days.