mysql

Enforces parameterized queries and strict settings for MySQL and MariaDB databases.

19|6|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/neverinfamous/memory-journal-mcp --skill mysql-neverinfamous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mysql
Source: https://github.com/neverinfamous/memory-journal-mcp/tree/main/skills/mysql
Command: npx skills add https://github.com/neverinfamous/memory-journal-mcp --skill mysql-neverinfamous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production-grade standards to prevent unsafe SQL practices in MySQL and MariaDB deployments, reducing risk of data loss and security issues.

Core Features & Use Cases

  • Enforces parameterized queries for all top-level statements to prevent SQL injection.
  • Requires safe read patterns with optional LIMIT and guaranteed transaction-scoped writes.
  • Enforces strict schema configurations (STRICT_TRANS_TABLES, ONLY_FULL_GROUP_BY) and explicit FOREIGN KEY usage.
  • Provides clear guidance for error handling and production diagnostics via MCP tooling.

Quick Start

Install the mysql-mcp server and configure it to enforce parameterized queries, guarded reads, and strict mode configurations for MySQL/MariaDB.

Frequently Asked Questions about mysql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce parameterized queries in MySQL to prevent SQL injection?

To prevent SQL injection, you must enforce parameterized queries for all top-level MySQL and MariaDB statements. This Skill automatically mandates strict parameterization across your database operations to eliminate unsafe SQL practices in production deployments.

What is the safest way to scope transactions and limit reads in MariaDB?

Safe read patterns in MariaDB require optional LIMIT clauses and guaranteed transaction-scoped writes. This Skill enforces mandatory transaction scoping for writes and guarded reads to protect destructive operations and maintain production-grade data safety.

How do I enable STRICT_TRANS_TABLES and ONLY_FULL_GROUP_BY for MySQL production standards?

Enabling STRICT_TRANS_TABLES and ONLY_FULL_GROUP_BY enforces strict schema configurations for MySQL and MariaDB. This Skill applies these production standards automatically, requiring explicit foreign key discipline and strict mode configurations to prevent data corruption.

Can I use this to apply foreign key discipline and strict schema modes in MariaDB?

Yes, this enforces explicit foreign key discipline and strict schema configurations like STRICT_TRANS_TABLES for MariaDB. It ensures your relational database management meets production-grade safety requirements by mandating structural integrity and strict data validation.

Why does my SQL deployment need guarded reads and protected destructive operations?

Your SQL deployment needs guarded reads and protected destructive operations to prevent accidental data loss and security vulnerabilities. This Skill enforces safe read patterns with optional LIMIT clauses and secures destructive operations through mandatory transaction scoping.

What are the limitations of relying on application-level validation for MySQL safety?

Relying solely on application-level validation leaves MySQL deployments vulnerable to SQL injection and schema corruption. This Skill overcomes those limitations by enforcing database-level strict modes, parameterized queries, and transaction scoping to guarantee production-grade safety.