Start a fresh conversation. Replace the highlighted placeholders.
Use database-security to produce a read-only hardening review checklist for the authorized [database type] environment [scope], covering network exposure/TLS, roles, sensitive-table access, risky configuration, audit logs, and backup permissions; do not probe, exploit, alter, extract data, or access credentials.
Required inputs
[database type]
[scope]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: database-securitydescription: "Authorized database security assessment across PostgreSQL, MySQL, MSSQL, MongoDB, and Redis: exposure, authorization gaps, UDF/command execution paths, and misconfiguration review."risk: offensivesource: "https://github.com/zhaoxuya520/reverse-skill"source_repo: "zhaoxuya520/reverse-skill"source_type: communitydate_added: "2026-08-25"license: "MIT"license_source: "https://github.com/zhaoxuya520/reverse-skill/blob/main/LICENSE"
⚠️ AUTHORIZED USE ONLY
This skill is for educational purposes or authorized security assessments only.
You must have explicit, written permission from the system owner before using this tool.
Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate
Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:
Ask the user to state the exact target URL, IP, account, or resource.
Ask the user to confirm written authorization and the permitted scope.
Show the exact command(s) and explain their expected effect.
Wait for explicit confirmation in the current conversation.
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
Database Security Assessment
When to Use
Assessing database hardening and exposure within an approved scope.
Checking authz boundaries and risky server-side execution features.