# Your AI tool can do everything your passwords can do

Security · For everyone · Published 2026-11-14 · Last checked against the source 2026-11-16
Web page: https://vibe.ikangai.com/notices/agent-credentials.html

> If your AI coding tool can read the passwords and secret keys for your live app, it can delete data or run up a bill while trying to help. An “Approve” button does not protect you if you click it without reading.

## Does this apply to you?

It applies if any of these is true:

- Your project has a file of passwords and secret keys for your live app (often called `.env`).
- You pasted a password or secret key into the chat or the settings of your AI builder.
- You are logged in to your hosting, database or payment provider in the same command-line window your AI tool uses.
- You let your AI tool run commands without asking you first.

## 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?

1. Ask your AI tool what it can reach. Paste this message and let it answer.

   Message to paste:

   ```text
   List every credential you can read or use right now: .env files in this project, command-line tools I am logged in to, and connected MCP servers. Do not print any secret values. For each one, tell me the worst thing you could do with it: delete data, spend money, or read customer data. Then propose a replacement that is read-only or works only on a development copy, and tell me which ones I should move out of your reach entirely.
   ```

2. Read the list it gives you. Anything that can delete data or spend money is the first to replace.
3. Swap the keys for your live app for safer ones. Use a key that can only read, or a test copy of your app, wherever the tool only needs to look. Keep the keys for your live app out of the project folder.
4. Turn approval prompts back on for anything that touches your live app, and read each one before you approve it.
5. If someone else looks after your app, send them this notice.

## Where this comes from

Kim Maida, Keycard. [Your Agent Is a Lethal Trifecta (And What to Do About It)](https://ai.engineer/talks/ws9XcGGPBDk-your-agent-is-lethal-trifecta-what-do). AI Engineer NYC 2026.

- [0:01 The demo: an AI tool with too much access](https://www.youtube.com/watch?v=ws9XcGGPBDk&t=1s)
- [4:16 Why useful AI tools are risky by design](https://www.youtube.com/watch?v=ws9XcGGPBDk&t=256s)
- [22:38 Why an approval button is not enough](https://www.youtube.com/watch?v=ws9XcGGPBDk&t=1358s)

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.
