Give agents narrow keys
Giving each agent the narrowest access key and spending limit that does the job. One mistake or breach then reaches little.
Konstantin's verdict: Trial
A key is a password-like code that lets software act inside an account. Before an agent takes a key, I have it weigh the damage that key could do against what it gains. It takes the narrowest key that does the job.
On 21 October an agent needed a key for a hosting account. It chose a key limited to a single project over a key for the whole account. That same day the hosting company, Railway, published a security notice. A narrow key limits the damage when a provider has a problem.
The same rule holds for money. My agents can spend only within a small limit that I set, and only after I approve the use.
What moved
On other radars
No community radar places this yet.
Sources
Share and embed
Makers: show where your product sits. The badge updates when the radar does.
Share this entry
Also in Practices · Trial
- Check every path through a user flowDrawing a user flow, such as a booking, as a chart of steps. A program then tries every order of steps, including retries and delays, to find where the user flow breaks.
- Guardrails, not manual reviewYou set the tests and limits once. Then agents ship without you checking each result.
- Let agents reach you by pushAgents bring questions and results to you, by text message, phone call or podcast, instead of leaving them in notes you must open.
- Pick a direction before agents build creative workFor creative work, agents first show several storyboards or directions. You pick one, then they build a rough version for fast feedback before any polish.
- Scheduled agent runsAgents run on a schedule and work through your inbox and task board. They fix what they can. You get only the decisions.