pii-safe-db-mcp@0.2.0
VERIFIED· install onlyPublisher claims: "Enables LLMs to run read-only queries against MySQL and PostgreSQL while detecting and masking PII in columns, values, and JSON/text fields before results reach the model." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
DATABASE_URLDB_PASSWORDPII_TOKEN_SECRETConfiguration, not credentials: ALLOWED_TABLES, AUDIT_ACTOR, AUDIT_ENVIRONMENT, AUDIT_LOG, AUDIT_QUERY_SHAPE, DB_HOST, DB_NAME, DB_PORT, DB_SSL, DB_TYPE, DB_USER, DENIED_TABLES, MAX_ROWS, PII_ALLOW_COLUMNS, PII_BLOCKED_COLUMNS, PII_EXTRA_COLUMNS, PII_MASK_MODE, PII_POLICY, PII_POLICY_FILE, PII_SCAN_VALUES, POLICY_FAIL_CLOSED, QUERY_TIMEOUT_MS- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for DATABASE_URL, DB_PASSWORD, PII_TOKEN_SECRET and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-08 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
"SELECT pg_read_file('/etc/passwd')",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."build": "tsc && chmod +x dist/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."SELECT LOAD_FILE('/etc/passwd')",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.