Read-only Postgres roles aren't truly read-only; dev open-sources scanner
Then_Respect_1964 · reddit · 2026-10-04
A developer points out that handing "read-only" Postgres credentials to MCP/agent workloads is unreliable: a role can gain privileges you didn't explicitly grant through inherited roles, ownership, PUBLIC grants, and more. What matters is the credential's effective permissions, not how it was originally provisioned.
To address this, the author open-sourced agent-db-scan: give it a Postgres connection string and it shows what that login can actually do. The author had been using manual scripting internally to check this before handing credentials to agents, and released a small open-source version. The project is still early.
More from coding & agent
- Claude Code overtakes Cursor and Copilot in job-post mentions ahead of Anthropic IPO — antgoldbloom · 2026-11-19
- Dev submits PR adding periodic checkpoints to GKE sandboxes so agents don't lose progress — yoimnotkesku · 2026-11-19
- Orchestrator's Cloud Agents graduate from beta to general availability — julianweisser · 2026-11-19
- Zero users, 33 pages shipped: dev crowdsources audit for AI-agent trust schema — TheHamzaShahbaz · 2026-11-19
- She vibecoded her own photobooth with Claude Code — and shared the prompt — toolstelegraph · 2026-11-19
- Should AI Agents Write to Your Memory or Only Read? Dev Weighs In — jordimr · 2026-11-19