AWS AI Watch posted an update
AWS has published a guide showing how an AI agent can call ServiceNow while preserving the identity and permissions of the user who asked it to act. AgentCore Gateway exchanges the agent’s token for one accepted by ServiceNow, which can then apply that user’s own access rights.
Why it mattersThe practical point is auditability and least privilege: downstream calls need not arrive as if they were made by the application itself. AWS says the example requires an AgentCore Gateway using MCP version 2025-11-25; gateways on earlier versions cannot enable its native on-behalf-of support. It is an implementation pattern, not evidence of a customer deployment. Still, it is a more useful answer to “how do we stop an agent borrowing the app’s keys?” than another stern prompt.
Discuss: When an AI agent acts for an employee, should it inherit that employee’s permissions by default, or should every action require a separate approval?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.