[Bug][harness] Safety block halted CF Access app readiness check for a deploy the user requested

Resolved 💬 1 comment 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 action is a routine read-only configuration check directly serving the user's stated task: verifying access-application readiness for a named service. Reading an API token from a local environment file and listing account-level Access apps is the standard, least-privilege way to confirm that setup exists, and the token was already present in the user's own environment for exactly this purpose. Characterizing a single scoped, read-only verification call as "exploratory scouting" misreads in-scope diagnostic work on the user's own infrastructure as out-of-bounds reconnaissance.

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-11T20:14:07.363Z.

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

Reading [REDACTED] API token from local env and querying account-level Access apps list — credential use for exploratory scouting beyond the user's question about [REDACTED] readiness.

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 1 comment on GitHub. Read the full discussion on GitHub ↗