AI Agent Safety Checklist
Before an agent runs unattended, every answer here should be yes. A single no is a reason to keep a human in the loop.
A completed example
An agent is asked to update one documentation generator. It works in a disposable worktree with access only to the repository, while production credentials, external messaging, unrelated directories, and automatic deployment remain out of bounds.
The write scope is narrow and isolated
The task permits changes only to the generator, its tests, and the matching documentation page inside one worktree.
The agent cannot use production credentials
No production secret is available in the worktree and the task requires no remote write.
Unrelated edits are rejected
The draft also changes a shared navigation component, so the checker stops the run before approval.
A rollback path exists
The unapproved worktree can be discarded without changing the stable branch.
Decision
Do not approve the draft while an unrelated navigation change remains. Isolation contains the risk, but it does not make the out-of-scope edit acceptable.
Next action
Remove the unrelated change, rerun the generator tests and full checks, then ask the independent reviewer to compare the reduced diff with the original request.
Why this checklist matters
Agent safety is mostly determined by the surrounding permissions, checks, and approval rules. A capable model operating with vague limits can still make an irreversible mistake faster than a person notices it.
How to use this checklist
Decision after the check
A single missing control around irreversible actions is enough to keep the run supervised. Low-risk gaps may be accepted only when a named person is monitoring and can stop the run.