Your AI agents see exactly what the user is allowed to see.
An agent wired with a technical account reads everything; the only guardrail left is the prompt. With akko-mcp-trino, every call carries the person's token down to Trino; that person's row filters and column masks apply, as they do for a dashboard.
What this means in practice
- Identity verified on every call (JWT), whatever the OIDC provider.
- Read-only decided on the SQL tree: a write hidden in a WITH or an EXPLAIN ANALYZE is refused.
- Bounds on every call: a row cap, a time budget per query and per call.
- One audit line per call, never the token.
- In AKKO and ARCHE, agent and access management, the complete audit and the business context of the catalogue come on top.
- The open source core, under the Apache 2.0 licence, reads under a configured identity or under each user's own, and installs with pip install akko-mcp-trino.