Memory Isn't Permission
Keeps what the agent remembers apart from what it may do today.
Granted vs Reached
Two lists, two minutes: what you think your agent can do, and what it can actually reach.
The ECHO line
If the second list is longer, you handed over a copy of the key when lending it would have done.
Run it before you connect anything new, and again after every tool update. It catches permissions wider than the job needs: sending when drafting was enough, a whole drive when one folder would do, access that never expires.
TO BE TESTED — RESULTS WILL BE SHAREDFrom our article "Who gave the agent the keys?"2 min5 of 5 free opens left
What it catches
Permissions wider than you think.
Setup time
2 min
Steps
- Write down what you think the agent can do, in three to five lines.
- Open its settings and write down what it can reach: the account it signs in with, whether it can send or only draft, which files, folders and calendars it can open, and how long each permission lasts.
- Compare the lists. Anything on the second list that isn't on the first is a key you handed over without meaning to.
- For each extra, remove it, shorten it to one time or one task, or move the job to a separate account that holds only what the job needs.
- Run the check again after any tool update or new connection.
What to do with the result
Shorten or remove every extra before you connect anything else. Keep your two lists; they're the baseline for the next check.
Run it with a second AI (optional)
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.