One governed MCP surface
Expose PostgreSQL without handing the model an unrestricted database connection.
PostgreSQL · MCP
Governed AI access to PostgreSQL.
Connect AI clients to PostgreSQL through hs-sql-agent's MCP surface, typed SQL compiler, access policy, Safe DML workflow, and audit boundary.
Dialect-aware compiler
Keep PostgreSQL-specific SQL semantics inside an explicit source/target capability boundary.
Policy before execution
Apply database scope, table policy, tool restrictions, rate limits, Safe DML, and audit before commit.
PostgreSQL stays behind a compiler boundary
hs-sql-agent does not treat a model-generated PostgreSQL statement as trusted simply because the provider could execute it. SQL first enters the typed validation and capability pipeline.
Provider support means the runtime can connect, inspect metadata, compile supported statements, and execute them under policy. It does not mean every vendor-specific syntax form is accepted automatically.
Use metadata before guessing schema
MCP clients can discover schemas, tables, and columns through the built-in metadata tools before constructing PostgreSQL SQL. This reduces blind schema guessing and keeps discovery inside the same authenticated database scope.
- get_schemas
- get_tables
- get_columns
- execute_query_sql
- execute_dml_sql
Fail closed when semantics are not proven
The PostgreSQL path follows the same rule as every other provider: unsupported syntax or cross-provider semantics are rejected at the appropriate validation/capability boundary rather than silently rewritten into a query with different behavior.