Least privilege means each person and each tool gets only what the job needs. Look-only where looking is enough. A practice copy where a practice copy is enough.
Time matters too. Access that runs out on its own is safer than access that lasts forever.
Actions that cannot be undone, like deleting data, changing the live website or moving money, deserve a person saying yes first, no matter who or what is asking.
Ask what happens if the tool, its keys or its instructions turn out to be wrong or stolen.
Words you will see
- Privilege
- What an account or tool is allowed to do.
- Read-only
- Permission to look but not change.
- Human in the loop
- A person must approve a risky action before it happens.
Decision
An AI helper needs to fix a small bug on your website. Which access is right?
What to do instead
- Start with look-only access.
- Ask a person to approve anything live or anything that deletes.
- Every few months, check who and what has access.
Common mistakes
- Granting admin to avoid permission errors.
- Never removing access after a project ends.
- Letting an AI agent use your personal, all-powerful token.
References and further reading
- Invariant Labs: GitHub MCP Exploited (least privilege recommended)Invariant Labs
- Supabase: Row Level SecuritySupabase Docs
Finished this one?
Add it to What I learned and earn 50 Trust. You can open your list from the badge at the bottom of the page.