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.
- Two principals distinguished, the calling product and the person it acts for; quotas and revocation.
- One audit line per call, never the token.
- A brick published under the Apache 2.0 licence, installable on its own on the Trino and directory you already have: pip install akko-mcp-trino.
Let us talk about your infrastructure.
A demonstration on your case, or a technical conversation.