Skip to content

Category 3 of 12 · Controls: What the agent may do

Agent authorization and fine-grained policy

Policy engines that decide, per tool call and per resource, whether an agent may act, including relationship-based and policy-based models and continuous re-evaluation instead of standing grants.

Mitigates: ASI02 Tool Misuse and Exploitation, ASI03 Identity and Privilege Abuse, LLM06 Excessive Agency

Vendors, by signal score

Ranked within this category only. How the score works.

Also covers this category

Questions to ask a vendor

  1. Can policy be expressed per tool and per resource, not only per app?
  2. Is authorization re-evaluated during a session, or granted once at login?
  3. Can retrieval be filtered to the requesting user's permissions?

Go deeper

FAQ

Why is authentication not enough for agents?
Knowing which agent is calling does not tell you whether this call, on this record, for this user, should be allowed. Agents chain many calls quickly, so the decision has to happen per action.
What is permission-aware retrieval?
A retrieval step that filters documents by what the person behind the agent is allowed to read before anything reaches the model, so the agent cannot summarise data its user could not open.