Ops Mysql Master Slave

ReviewAudited by ClawScan on May 6, 2026.

Overview

This is an instruction-only MySQL operations runbook whose powerful database and server commands match its stated purpose, but users should review them carefully before running anything on production systems.

Install this skill only if you want an operational MySQL replication and migration runbook. Treat its commands as production DBA actions: verify hosts and paths, use secure credentials, back up before restore, and do not let an agent execute destructive commands without explicit review.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Medium

#ASI02: Tool Misuse and Exploitation

What this means

Running these commands incorrectly could stop MySQL or delete production database files.

Why it was flagged

The restore procedure includes privileged service control and a destructive deletion of the MySQL data directory. This is expected for a database restore runbook, and the artifact includes a warning, but it is still high-impact if copied or executed on the wrong host.

Skill content

systemctl stop mysqld

# Clear data directory
rm -rf /var/lib/mysql/*

Recommendation

Only run restore steps after verifying the target host, backup validity, and having a current snapshot or rollback plan; require explicit human approval before destructive commands.

Medium

#ASI03: Identity and Privilege Abuse

What this means

Misusing or exposing these credentials could grant broad database access.

Why it was flagged

The SOP uses MySQL administrative credentials for backups. This is purpose-aligned for database migration, but it involves highly privileged account access and placeholder credentials.

Skill content

xtrabackup --backup \
  --target-dir=/tmp/backup_full \
  --compress \
  --compress-threads=4 \
  --user=root \
  --password=password

Recommendation

Use least-privilege backup or replication accounts where possible, replace placeholders with secure secrets, and avoid logging or sharing command lines containing passwords.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

The installed package depends on trusting the remote repository and whatever version is current at install time.

Why it was flagged

The setup instructions install a repository package from a remote 'latest' URL. This is expected for installing Percona XtraBackup, but it is not pinned to a specific package version or checksum.

Skill content

yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
yum install -y percona-xtrabackup-24

Recommendation

Prefer vendor-documented installation, verify package signatures, and pin versions where operational reproducibility matters.