Enforcing RBAC for AI agents with a database proxy: one team's open-source setup
Grouzoul · reddit · 2026-10-16
A team shares how they stopped leaking DB credentials to agents:
- Dropped local secret managers: credentials scattered across browsers, memory, Slack; cleanup surface too large, and poor visibility into agent permissions (they point to Infisical's open-source option).
- Rejected LLM-based MCP proxies like Query Shields: natural-language endpoints where a proxy LLM rebuilds queries are token-hungry and an unsecured black box.
- Final setup: d9 (an open-source community fork, author is a maintainer) as a proxy that generates secure APIs with fine-grained permissions over the existing DB, acting as the agents' auth provider with rotating tokens; Keycloak handles human SSO and ties each agent to a responsible human, with 2FA when needed.
Simple to deploy, with real-time visual supervision of each agent's permissions and activity.
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23