1. Describe how customers configure the set of actions an agent is permitted to take, including whether permissions can be scoped per action type rather than granted as a single bundle.
Why it matters. All-or-nothing permission models force customers to over-grant authority to agents, expanding blast radius from any single failure or prompt injection. OWASP LLM06:2025 Excessive Agency names excessive permissions as a root cause and recommends limiting permissions to the minimum necessary. This question screens vendors whose permission model is too coarse for regulated environments.
- Describes named permission primitives at per-action or per-tool granularity.
- References a policy or role configuration surface (UI, API, or IaC).
- Distinguishes read-only actions from state-changing actions.
- Only a single 'agent enabled' toggle exists.
- Permissions inherit entirely from the user session with no agent-specific scoping.
- Permission model described only in marketing language without enumerable scopes.