Agents invent column names. The usual result is a failed query, an error the model has to interpret, and two or three more round trips before it gets there.

validate_sql checks a statement against the schema the credential is actually allowed to see and reports unknown relations and columns without executing anything. It is oracle-safe: a column the policy masks or denies does not become discoverable by asking whether it validates.

That brings the hosted MCP endpoint to eight tools: query, validate_sql, list_tables, describe_table, explain, schema_catalog, search_docs, and read_doc. The catalog also now carries your own table and column comments, so an agent reading your schema gets the descriptions your team wrote rather than guessing from names.

validate_sql on the hosted MCP endpoint

Give your agent Postgres it can't wreck