[Bug][harness] Safety block halted authorized re-provisioning of a leak-free, API-restricted cloud LLM key aft

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

Why this is a false positive

The safety system flagged routine cloud IAM key rotation as resource hijacking, but the work is legitimate and in-scope: the affected credential was confirmed never committed to version control, the repository is private, billing and authentication were already valid, and the replacement key was created with a single-service restriction so it cannot reach any other API even if exposed. The original suspension stemmed from a benign traffic pattern on a disposable, auto-generated development key, not a compromise, and every step taken was standard remediation under an authorized, owner-controlled account. The block message provided no reason, leaving no signal to distinguish this from an actual abuse scenario.

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

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

No reason provided

Environment: Claude Code, Linux. · Work domain: cloud-iam

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