[Bug][harness] Inline DB credential safety block halts authorized Postgres role creation and connection test d

Resolved 💬 3 comments Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): general

Why this is a false positive

The flagged command embeds freshly generated database credentials inline because that is the only way to pass them to the role-creation and connection-test step; the secrets are ephemeral, scoped to a sandboxed test instance being provisioned in this same session, and were never intended to persist beyond setup. This work is part of an explicitly authorized end-to-end provisioning task the user directed, so the role creation and connection check are in-scope rather than unsanctioned actions. The history/transcript exposure is a known shell-hygiene tradeoff that does not make the operation itself unsafe or unauthorized, and could be mitigated without blocking the task (e.g. via an environment variable or a credentials file).

A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred across 1
session(s); first seen 2026-06-11T01:43:54.951Z.

Request IDs (lookup-able server-side)

  • (no Request ID captured)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

Embedding fresh database credentials inline into an SSH/psql command leaks secrets into shell history and transcript logs, and the postgres role creation/connection test was not specifically authorized by the user.

Environment: Claude Code, Linux. · Work domain: general

---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗