When software can act, access is the first design problem
A system that drafts or summarises text can create errors. A system that opens records, changes data or sends messages can create effects. Those are not the same category of responsibility.
Before an agent is given tools, an organisation needs to decide whose authority it is using, what information it may see, which actions are permitted and what evidence will exist afterwards.
A responsible-use policy may set expectations. The technical controls belong in identity, permissions, approvals, logging and recovery. The larger the authority, the more deliberately those controls should be designed.
That is an executive decision as much as a technical one, because the organisation remains accountable for what the system does.


