[Bug][harness] SSH read of prod container code blocked while debugging devtools-blocker, 500 errors, and Index

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

Why this is a false positive

This block flags a routine read-only SSH operation against a defensive-hardening target as if it were unauthorized access to production, but the SSH credentials, fleet map, and access patterns were supplied by the user through an explicitly loaded access-management skill that scopes the work to these containers. The earlier rejected SSH attempt was a different command to the same host, not a denial of this read, so treating the prior rejection as standing disapproval conflates two distinct operations. The action is an in-scope diagnostic read (investigating a 500 error and a broken client-side blocker) on infrastructure the user owns and has granted access to, making the "without explicit user approval" determination incorrect.

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

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

SSH read into shared production container [REDACTED] (Production Reads) without explicit user approval naming the prod target, and a similar [REDACTED] SSH was rejected by the user earlier.

Environment: Claude Code, Linux. · Work domain: defensive-hardening

---
_{🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.}