db-connector

To run a read-only SQL query safely, use a policy gate that checks every statement before any driver loads or connection opens. This mechanism blocks unsafe operations, escalates writes for approval, and returns structured JSON results for safe analytics.

During database schema introspection, attempting a delete or admin operation triggers a hard denial for privilege statements. The system returns the formatted SQL for delete or admin operations without executing them, ensuring the underlying database remains protected.

Yes, you can query multiple database engines including PostgreSQL, MySQL, SQLite, SQL Server, MongoDB, DynamoDB, and Oracle. The connector framework uses pluggable drivers to support these diverse environments while maintaining consistent read-only safety.

To retrieve table and column names, use the schema introspection action with optional filtering. You can apply table-name patterns like users% to selectively list tables and columns, returning the discovery results in a structured JSON envelope.

The policy gate blocks write operations before the database connection opens. It enforces read-only safety by validating every statement prior to any driver load or connection initialization, guaranteeing that unsafe queries never reach the underlying database drivers.

Query results are returned in a JSON envelope with status codes to guarantee safety behavior and provide structured output. This format includes relevant fields and status indicators, ensuring consistent handling of controlled result truncation and blocked operations.