Acting on someone’s behalf is not the same as being them. How we scope what an agent can read and change.
A thought to take with youGive each tool only the access its task needs, and ask a person before anything sensitive is changed.
The risk
It is easy to let an agent run with the same access as the person using it. If that person is an administrator, a single misunderstood instruction can now change or delete far more than intended.
How we scope access
Each tool the agent can use gets its own narrow access: read-only where possible, and limited to the records the task involves. Changes that are hard to undo, such as payments, deletions or messages to customers, always wait for a person to confirm.
Every action is logged with who asked for it and what the agent did, so it can be reviewed later.