Least privilege
Read-only Postgres for AI agents
Block every INSERT, UPDATE, DELETE, and DDL per credential. Reads pass, writes are rejected in the wire protocol before they ever reach your database. No database role juggling.
Postgres roles can enforce read-only, but managing a role per agent across databases is fiddly, and a role does not give you allowlists, masking, budgets, or an audit trail. PgBeam enforces read-only per credential at the wire, so a write never reaches the database, and layers the rest of the policy on top.
Writes blocked before they land
Mark a credential read-only and every INSERT, UPDATE, DELETE, and DDL is rejected in the proxy. The statement never reaches your database, and the agent gets an LLM-readable reason it can act on.
An UPDATE or DELETE without a WHERE clause is blocked outright for agent credentials, so a mistaken statement cannot rewrite a whole table even where writes are allowed.
More than a role
Read-only is the floor. Add table and column allowlists, row-level WHERE filters, PII masking, and query budgets to the same credential.
Policies stream to the proxy and hot-reload, so flipping a credential between read-only and read-write takes effect on the next query, with no role changes in the database.
Per-credential
Read-only is set on the credential, not the database role, and changes instantly.
Allowlists
Restrict reads to the exact schemas, tables, and columns the agent should see.
Row-level policies
Scope an agent to a slice of a table with a WHERE filter applied to every read.
Audited
Every blocked write and allowed read is recorded with its reason.
Questions
Give your agent safe Postgres access
Start with a 14-day free trial. No credit card required.
Technical preview. For internal testing only.
Get Started