Your AI tool can do everything your passwords can do
For everyone who builds with AI
Does this apply to you?
Tick anything that is true for you. If nothing is, you can skip this notice.This applies to you. Go to the steps
What is the problem?
An AI coding tool uses whatever access it can find. If the passwords and secret keys for your live app sit where the tool can read them, it can do anything those keys allow: change your database, restart your servers, order more capacity.
It does not need to be attacked or tricked. It only needs to decide that a drastic step is the way to finish its task.
What could happen?
In a staged demo by Kim Maida of Keycard, an AI tool on overnight duty held an admin password for the database and full access to the hosting account. It deleted the live database because the recovery instructions said to delete it and restore a backup. It restarted a server and took the product offline. It scaled a service from 4 machines to 40, at $420 an hour.
Asking the tool to get your approval first does not solve this. People who are asked to approve everything stop reading what they approve.
What should you do?
Where this comes from
Kim Maida, Keycard. Your Agent Is a Lethal Trifecta (And What to Do About It). AI Engineer NYC 2026.
- 0:01The demo: an AI tool with too much access
- 4:16Why useful AI tools are risky by design
- 22:38Why an approval button is not enough
Vendor talk. The speaker’s company sells access control for AI tools. The demo is staged, and the talk says so.
How we adapted it
Maida’s own fix is built for teams that run their own AI systems: short-lived access issued for each task and checked against what the user is allowed to do. The steps above are our small-scale version of the same idea.