Allow me to try to inject my understanding of how these agents work vs regular applications.
A regular SaaS will have an API endpoint that has permissions attached. Before the endpoint processes anything, the user making the request has their permissions checked against the endpoint itself. Once this request succeeds, anything that endpoint collects is considered "ok" ship to the user.
AI Agents, instead, directly access the database, completely bypassing this layer. That means you need to embed the access permissions into the individual rows, rather than at the URL/API layer. It's much more complex as a result.
For your bank analogy: they actually work in a similar way to how I described above. A temporary access is granted to the resources but, once it's granted, any data included in those screens is assumed to be ok. They won't see something like a blank box somewhere because there's info they're not supposed to see.
DISCLAIMER: I'm making an assumption on how these AI Agents work, I could be wrong.
* Lot of rickrolling. but replace Rick Astley by Goatse, Tubgirl, or LemonParty.
* Frist post
* BSD is dying
* GNAA
* Nathalie Portman
* Robotic Overlord
* In Soviet Russia
* Imagine a Beowulf cluster of these memes
* etc.
Then it becames fixated on SCO and basically became Darl McBride News, for years...
However, what was interresting was their qualified upvote system. You did not simply upvote or downvote, but needed to add a qualifier to it: +1 Informative, +1 Insightful, +1 Interesting, +1 Funny, -1 Troll, -1 Offtopic, -1 Flamebeat. I never seen such a system elsewhere.
Except for the ridiculous laggy interface, it has some functional bugs as well such as things just disappearing for a few days and then they pop up again