SafeDB MCP
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
SafeDB MCP is a secure Model Context Protocol server that lets AI agents inspect and query Postgres, MySQL, MariaDB, and SQLite with strict read-only guardrails. It is designed for teams that want useful database access without handing an agent unrestricted production credentials.
Direct database credentials are dangerous for agents because a single bad prompt, tool call, or generated SQL statement can mutate data, exfiltrate sensitive columns, or run expensive queries. SafeDB MCP puts a policy layer between the agent and your database: only configured schemas and tables are visible, SQL is parsed and validated before execution, row counts are capped, results are masked, and every query attempt is audited.
This project is an MVP. It prefers false positives and blocked queries over unsafe access, and it does not claim perfect SQL security.
Features
- MCP tools: list_schemas, list_tables, describe_table, run_readonly_query, explain_query, get_safedb_policy
- Postgres support through pg
- MySQL and MariaDB support through mysql2
- SQLite file support through sql.js
- YAML or JSON config with environment expansion
- AST-backed read-only SQL guardrails for SELECT, WITH ... SELECT, UNION, and EXPLAIN SELECT
- Table detection through joins, CTEs, nested subqueries, aliases, and unions
- Column projection checks that block masked fields selected through aliases or expressions
- Configurable table allowlists, denylists, row limits, and statement timeout
- PII masking: redact, email, partial, and deterministic hash
- JSONL audit log with no raw result data
- CLI binary: safedb-mcp
- TypeScript, Vitest, ESLint, Prettier
Quickstart
Use a dedicated database role with read-only permissions. SafeDB MCP is a defense-in-depth layer, not a replacement for least-privilege database credentials.
Docker
A Docker image packages SafeDB MCP with Node.js and its production dependencies so it can run the same way on any host with Docker.
Build the image locally:
Run the MCP server with a mounted config file:
Pass CLI commands after the image name:
Example Config
For MySQL or MariaDB, set database.type and use the database name as the access schema:
For SQLite, set database.type to sqlite, point database.path at the .db file, and use main as the access schema:
MCP Client Config
Claude Desktop:
Cursor or Hermes-style MCP config:
Security Guarantees
SafeDB MCP aims to guarantee that:
- Only configured schemas and tables are inspectable or queryable through the MCP tools.
- SQL is parsed before execution, and mutating statement types or multiple statements are blocked.
- Table access policy is checked against real tables found through joins, CTEs, nested subqueries, aliases, and unions.