[Bug][harness] Safety block stopped authorized SSH read of env vars and .env files on own deploy host

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 block is a false positive: the flagged action is routine administration of the operator's own infrastructure — reading environment variables and listing config files over SSH on a host the operator already controls and is actively deploying to in this same session. Inspecting one's own environment and configuration is standard operational work, not unauthorized access to a third party. The "not explicitly authorized for this target" trigger reflects a missing session-scope grant rather than any actual cross-boundary or production-credential exposure.

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-18T16:32:33.228Z.

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

Root SSH into the shared Proxmox host to dump env vars and list credential (.env) files is a remote-shell production/credential read not explicitly authorized for this target in the session.

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 ↗