A developer whose AI agent nearly ran a destructive query through a supposedly read-only Postgres login found that role inheritance, table ownership, and indirect grants made the login more powerful than intended. They built agent-db-scan, an open-source tool that audits a Postgres connection's effective privileges. It matters to anyone giving database credentials to agents.
A practitioner post lays out four ways LLM agents can still damage a Postgres primary even when pointed at a read-only replica: replication bloat, privilege gaps, audit blind spots, and masked-view friction, each with a concrete fix. It matters to anyone giving agents database access, since read-only setups alone don't stop long-running queries from degrading production performance.
A practitioner post lays out four ways LLM agents can still damage a Postgres primary even when pointed at a read-only replica: replication bloat, privilege gaps, audit blind spots, and masked-view friction, each with a concrete fix. It matters to anyone giving agents database access, since read-only setups alone don't stop long-running queries from degrading production performance.
An engineer auditing an internal AI agent found it ran under a broad IAM role with keys far wider than the read-only access its job required. Agent frameworks inherit the developer's identity, making blast radius the union of everything that identity can reach. The practitioner community is being asked how it schedules agent identity audits and scopes permissions at creation.
An engineer auditing an internal AI agent found it ran under a broad IAM role with keys far wider than the read-only access its job required. Agent frameworks inherit the developer's identity, making blast radius the union of everything that identity can reach. The practitioner community is being asked how it schedules agent identity audits and scopes permissions at creation.
A prompt that can be given to AI agents like Claude or Codex to automatically verify Row Level Security policies on every table in a Supabase project. It helps developers ensure their database security policies are correctly configured.
A prompt that can be given to AI agents like Claude or Codex to automatically verify Row Level Security policies on every table in a Supabase project. It helps developers ensure their database security policies are correctly configured.
A read-only SQL file that scans a Supabase database for five common Row Level Security misconfigurations introduced by AI coding tools like Lovable, Bolt, Cursor, and Replit. It helps developers and security auditors quickly identify data exposure risks without modifying any data.
A read-only SQL file that scans a Supabase database for five common Row Level Security misconfigurations introduced by AI coding tools like Lovable, Bolt, Cursor, and Replit. It helps developers and security auditors quickly identify data exposure risks without modifying any data.
A developer shared pg-dry-run on Hacker News, a tool that lets AI agents preview Postgres writes before committing them using xmin checks. It targets the practical problem of letting agents run safely against production databases. Interest so far is minimal, with low engagement on the launch post.
A developer shared pg-dry-run on Hacker News, a tool that lets AI agents preview Postgres writes before committing them using xmin checks. It targets the practical problem of letting agents run safely against production databases. Interest so far is minimal, with low engagement on the launch post.