Comment by sksksjjweu

I am not convinced this is the deep issue everyone thinks it is.

SQL injection is exactly as dangerous. It gives unfettered access to all DB operations that the query user was allowed to perform. One mitigation was prepared statements, but the other is not allowing unfettered access to the database as any user. A reading user should not be allowed to DROP TABLE, SQL injection or not.

This agent has unfettered read access and has no concept of the “recipient” of the answer. It would be quite trivial to include the recipient’s authorization and thus be denied reading access automatically. Of course this is not the only solution, but it’s not hard to think of solutions in that direction.

Your “menu” example is exactly what hasn’t changed. LLM or human employee: they are only allowed a fixed set of controlled actions. Their freedom is formulation mainly, but their authz is a fixed set. I don’t see how they need to be “more” than a menu.