Execute SQL Queries Against Databases

This toolkit executes SQL queries against SQL databases, with support for both read-only and read-write modes. It currently supports DuckDB and SQLite, with extensibility noted for MySQL and other SQL databases. Configuration includes an optional database_path (defaults to an in-memory database if not set; for DuckDB and SQLite, use :memory: for in-memory or a file path for persistent storage), a database_type literal currently accepting "duckdb" or "sqlite" (default "duckdb"), a read_only flag that, when True, restricts execution to SELECT queries and rejects write operations (INSERT, UPDATE, DELETE, etc.), and a timeout for database operations in seconds, defaulting to 180.0 if unspecified. It raises a ValueError if database_type is unsupported, and an ImportError if the required database driver isn't installed.

Use it when an agent needs to run SQL queries against a DuckDB or SQLite database, whether in-memory or file-backed, and needs an enforced read-only mode to prevent accidental writes.

Do not use it for database types beyond DuckDB and SQLite without confirming driver support first - unsupported types raise a ValueError, and a missing driver raises an ImportError.

Input is SQL queries plus the toolkit's configuration: database_path, database_type (duckdb or sqlite), read_only, and timeout. Output is the query execution result; in read_only mode, only SELECT queries execute and any write operation is rejected outright.

Supports DuckDB and SQLite natively, with the codebase noting extensibility toward MySQL and other SQL databases.

Developers building agents that need to query or, when explicitly allowed, modify a DuckDB or SQLite database, with a built-in safeguard to enforce read-only access when needed.