Permission-aware RAG in Go: the model never says who the user is
My pdf-mcp server had no access control: the model picked the customer. permission-aware-mcp fixes that. Identity comes from a verified token and the database, search filters by permission before it ranks, and every read is rechecked and audited. Four users asking the same question get four different answers, and a planted prompt injection still can’t reach a confidential document.