Model Context Protocol moderate risk

Dbhub

DBHub is a zero-dependency MCP server enabling database access (PostgreSQL, MySQL, SQLite, etc.) for MCP clients with safety controls and multi-database support.

Connections & Capabilities

Connects To

GitHubPostgreSQLMySQLSQLiteDocker

Capabilities

readwriteexec

Quickstart

Install

npx @bytebase/dbhub@latest --transport http --port 8080 --dsn "postgres://user:password@localhost:5432/dbname?sslmode=disable"

Exposed MCP Tools (3)

high

execute_sql

Executes SQL queries against the configured databases, supporting transactions.

Allows arbitrary SQL execution, potentially leading to data modification or deletion.

safe

search_objects

Searches and explores database schemas, tables, columns, and other database objects.

Read-only operation that does not modify data.

critical

Custom Tools

Executes user-defined SQL operations defined in the configuration file.

The danger level depends entirely on the SQL defined in the custom tool, which could be anything.

Safety Assessment

DBHub offers several safety features, but the ability to execute arbitrary SQL queries means careful configuration and monitoring are necessary. It's safer in read-only mode with strict row limits and query timeouts. Risks increase with write access and custom tools.

Read-only mode available to prevent unintended writes.
Row limiting to restrict the amount of data returned.
Query timeout to prevent long-running queries.
SSL/TLS encryption for secure communication.

Direct SQL execution is possible, which can be risky if not carefully controlled.
Potential for SQL injection if input sanitization is not properly implemented in custom tools.
Access to multiple databases simultaneously increases the attack surface.
Improperly configured SSH tunneling can expose databases.