What permissions should an AI agent have?

An AI agent should have only the permissions its one job needs. If it summarizes email, it needs read access to one inbox, not send rights or your whole drive. Start read-only, give it its own account, limit folders and tools, and make high-impact actions like sending, paying or sharing wait for a person.

Why does an AI agent need its own account?

So you can see and limit exactly what it does. If an agent runs under your login, it gets everything you can reach, and its actions look like yours in the logs. A separate account lets you grant narrow access, review its activity on its own and shut it off without locking yourself out.

How do you limit an AI agent to the tools it’s allowed to call?

List the tools the job needs, connect only those, and remove the rest. OWASP‘s guidance on excessive agency says to minimize extensions, minimize their functionality and minimize their permissions. In practice, if an agent only needs to read a calendar, don’t connect a tool that can also edit or delete events.

Be careful with “all-in-one” connectors. A single email connector may read, send, delete and forward. If your platform lets you, turn off the actions the job doesn’t need. If it doesn’t, give the agent’s account only read rights at the source, so a send request fails even if the agent tries.

This matters because agents can be misled. A hidden instruction in an email or web page can push an agent to act, which is called prompt injection. Our guide to what prompt injection is explains how. Tight permissions limit the damage.

What is a kill switch for an AI agent, and how do you test it?

A kill switch is one fast way to stop an agent from acting, such as disabling its account, revoking its access tokens or pausing its workflow. Test it before launch: start a harmless task, trigger the switch, and confirm the agent stops and can’t reach your data. Write down who can flip it and how.

What else belongs on an AI agent security checklist?

Beyond permissions, an AI agent security checklist covers six more items: keep passwords and API keys out of prompts, treat emails and web pages as untrusted input, check what the vendor stores or trains on, record the agent and its owner in your AI tools register, test it on fake data before go-live, and review it every quarter.

Get a ready-made AI tools register in our free AI acceptable use policy template kit. Insurers ask about this too: see cyber insurance AI questions on human review and logging.

New to agents? Start with our guide to AI agents for small business, which covers a safe first read-only job. For a review of the agents and AI tools you already run, see our AI security assessment.

AI agent permissions: frequently asked questions

Leave a Reply

Your email address will not be published. Required fields are marked *