Per-role identity
Each Sembric role uses its own restricted login and runtime-only password reference. TLS certificate and hostname verification is always on, and an operator allowlists the exact host, port and database.
Integration · Native PostgreSQL
Governed PostgreSQL access for AI agents
Connect an existing PostgreSQL schema over verified TLS with a restricted login per Sembric role, keeping row-level security in force.
Identity
How Sembric connects to PostgreSQL
Your policies stay in force
Row-level security and column grants stay in force. Superusers, BYPASSRLS logins and table owners can bypass row policies, which is why Sembric refuses those mappings.
Enforcement
What Sembric checks and refuses
- On every connection, before the data statement, Sembric refuses administration, BYPASSRLS, schema creation, relation ownership and write privileges in the chosen schema.
- Reads run in read-only transactions with $n parameters, server statement timeouts and bounded streaming responses.
- Composite, array, domain and enum types keep their full definitions in the reviewed fingerprint.
- Source connections never reuse Sembric’s own metadata database credentials, pools or type parsers.
Limits
What these controls don’t do
- Time and response controls do not cap scan bytes or server cost; set connection limits and resource controls on your server.
Setup
Connecting PostgreSQL
- Create a separate login per Sembric role with CONNECT on the database, USAGE on the schema and SELECT on approved tables, views or columns only.
- Have an operator allowlist the exact endpoint and provision each role’s password as a runtime secret (and a private CA bundle if you use one).
- An owner enters the endpoint, schema, logins and secret references and tests every mapping.
- Discover, review classifications and certify with an independent reviewer.
FAQ
PostgreSQL questions
Will PostgreSQL row-level security still apply?
Yes. Queries run as the login mapped to the caller’s role, and Sembric refuses logins that could bypass row policies, such as superusers, BYPASSRLS roles and table owners.
Can we turn off TLS for a private network?
No. Certificate and hostname verification is always enabled. Use a private CA bundle if your server is not signed by a public authority.
Other integrations
Put your first certified data product in front of an agent.
Tell us which warehouse you run and what your agents need to answer. We will help you connect a source, certify a first surface and query it over MCP.