Security audit
Security checks for vulnerabilities and agentic risk
This is a MySQL reference skill made of Markdown guidance, with no executable code, hidden installation behavior, persistence, or credential handling.
Installers should treat this as a database-administration reference: useful, but any generated SQL that mutates schema, terminates sessions, or changes production data should still be reviewed and approved by a human before running against real databases.
The document notes that REPLACE INTO deletes then inserts and may trigger DELETE cascade, but it does not explicitly warn users that this can remove related data or fire destructive side effects. For markdown files, safety-relevant behaviors affecting user data should be clearly called out as warnings, not only described as a technical nuance.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## EXPLAIN First
Never ship a query without checking EXPLAIN. Key columns:
- `type`: ALL = full scan (bad), range = index range (ok), ref = index lookup (good), const = single row (best)
- `rows`: estimated rows examined—multiply across joins
- `Extra`: "Using filesort" = sorting without index, "Using temporary" = temp table
The markdown states that ALTER TABLE commits immediately and cannot be rolled back, but it does not frame this as a user warning about irreversible schema changes. Because this behavior can affect data integrity and recovery expectations, the documentation should explicitly warn users before they rely on rollback safety.
This markdown skill includes KILL <id>, which can terminate running database sessions, but the document provides no explicit user warning about potential disruption to active work. Under the markdown-file criteria for SQP-2, user-facing documentation should disclose behaviors that may affect system integrity or availability.
No suspicious patterns detected.