Connect to a database.

Disconnect from a database.

List all currently active database connections.

Returns alias, dialect, permission mode, and connection time.

Reconnect to a previously saved connection from the OS Keyring.

List all tables in the connected database with row counts and sizes.

The editor AI uses this to understand the database structure before generating queries. Schema is served from cache when available.

Show full column definitions, types, constraints, and indexes for a table.

Includes: column names, data types, nullable, primary key, unique, foreign keys. The editor AI reads this to understand the exact schema before generating queries.

Preview a few rows from a table to understand its data shape.

Useful for the editor AI to understand the actual values in the database before generating queries (e.g., what status values exist, date formats, etc.)

Force a schema cache refresh for a connection.

Call this after CREATE TABLE, ALTER TABLE, or any DDL operation to ensure the AI has up-to-date schema context.

Dry-run a query through the full safety + intent pipeline.

Returns:

• Safety verdict (SAFE / BLOCKED with reason)

• Intent analysis (interpreted intent, assumed filters, ambiguity warnings)

• EXPLAIN cost estimate (PostgreSQL only)

• Final SQL with auto-LIMIT applied

For bare SELECT * queries on large tables, Bollard will automatically redirect to profile_table to give the AI richer context with fewer tokens.

The editor AI should call this before execute_query for any non-trivial query.

Execute a SQL query through the risk-tiered safety pipeline.

Generate a statistical profile of a database table.

All aggregation is performed directly in the database via SQL queries. No rows are transferred to local memory. Returns a compact Markdown summary suitable for AI context (< 150 tokens overhead per column).

Includes for every column:

• Row count and null percentage

• Distinct value count

• Min / Max / Avg (numeric and date columns)

• Top-5 value distribution for categorical columns (<= 100 distinct values)

Log a query correction for future AI context.

When the editor AI generates a wrong query and the user corrects it, log the correction here. Bollard persists it and exposes it via the bollard://corrections/{alias} MCP Resource, so the AI automatically learns from past mistakes without the user repeating themselves.

Return recent query history for a connection.

Useful for the editor AI to understand what has been executed recently, especially when the user says "run that again" or "fix the last query."

Return all logged corrections for a connection.

The editor AI reads this via the bollard://corrections/{alias} MCP Resource automatically. Call this tool directly to inspect them.