Free permissions checklist
AI Agent Permissions Checklist
Review permissions by effective capability. The integration name tells you where an agent connects; the permission tells you what can happen.
Inventory every connection
Include direct APIs, OAuth apps, browser sessions, shared accounts, automation platform credentials, databases and file stores.
- Tool, account and environment.
- Credential owner and rotation process.
- Permission scopes granted.
- Data categories available through the connection.
- Reason the connection is needed.
- Last verification date.
Review read access
Read access can expose more than the workflow uses. Check whether queries, folders, mailboxes or repositories can be narrowed.
- Customer messages and contact records.
- Employee, candidate or payroll information.
- Contracts, financial records and payment details.
- Private source code, tickets and documentation.
- Secrets, credentials or environment configuration.
- Historical data beyond the workflow’s purpose.
Review write and action access
Describe each operation and whether it is reversible. “Write” may cover a harmless draft or a production deletion.
- Create, update and delete records.
- Send email, chat messages or public content.
- Merge code, deploy software or change infrastructure.
- Issue refunds, payments or credits.
- Invite users or change access rights.
- Trigger downstream workflows and webhooks.
Check boundaries and safeguards
Least privilege is an operating practice. Confirm the boundary in the tool rather than relying only on prompt instructions.
- Use a dedicated identity where practical.
- Limit workspace, repository, folder or record scope.
- Separate read and write credentials.
- Require approval for higher-impact operations.
- Set rate, value, destination or time limits.
- Log actions and test revocation.
Practical advice
Ask the owner to demonstrate one normal action and one blocked action. This often reveals the difference between intended and effective access.
Review permissions again after workflow changes. A new step may reuse a credential that was acceptable for the original purpose but is too broad for the new one.
FAQ
Questions people ask before a review
Map each permission to the agent that uses it.
Keep access, safeguards, findings and remediation together in Roxea.