Safe MySQL FAQs

Question 1

What types of SQL operations can be controlled or restricted?

Accepted Answer

Safe MySQL provides granular control over SQL operations. Administrators can define allowlists for DML (SELECT, INSERT, UPDATE, DELETE) and DDL (CREATE TABLE, ALTER TABLE, CREATE INDEX) statements, while explicitly blocking dangerous operations like DROP or TRUNCATE. It also enforces query timeouts and row limits.

Question 2

What is Safe MySQL and its primary purpose?

Accepted Answer

Safe MySQL is a secure gateway that enables AI tools, such as Claude Code, to safely interact with MySQL databases using the Model Context Protocol (MCP). Its primary purpose is to provide robust SQL validation, access control, and comprehensive observability for secure database operations in development and testing environments.

Question 3

How does Safe MySQL ensure database security?

Accepted Answer

Safe MySQL ensures security through robust SQL parsing and validation, fine-grained DML/DDL control, automatic LIMIT application for dangerous operations, JWT authentication for secure access, and a comprehensive audit trail that logs all database interactions.

Question 4

What kind of observability features does Safe MySQL offer?

Accepted Answer

It offers detailed observability through Prometheus Metrics, tracking HTTP requests, database queries, security violations, and MCP calls. Additionally, it provides comprehensive audit logging with JSON format, log rotation, and compression for a complete record of all activities.

Question 5

Can Safe MySQL be easily integrated into existing infrastructure?

Accepted Answer

Yes, Safe MySQL is designed for easy integration. It offers production-ready Docker support, allowing quick setup with `docker-compose`. Its configuration supports hot reloads, enabling updates to database connections, security rules, and audit settings without restarting the server.

Safe MySQL

Safe MySQL

Key Features

Use Cases

Key Features

Use Cases