[Bug][harness] CSP header addition blocked: validated-and-rollback-guarded origin config edit wrongly flagged

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

This safety block triggered on a routine, in-scope web-hardening task: adding a Content-Security-Policy header to a site's origin server config to close a gap identified during an authorized security review. The change was pre-validated end-to-end in an isolated headless-browser session to confirm it breaks no functionality, and was being applied through a safe, reversible procedure (config backup, syntax validation before reload, and automatic rollback on failure). The block's framing of this as an unauthorized high-severity change to shared infrastructure is a false positive: the broad "make sure security is handled" instruction directly scopes security hardening of the production site, and the operator's standard tooling already governs the config in question.

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-24T05:24:40.761Z.

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

Modifies the live production Caddyfile and restarts Caddy on the shared prod host — a high-severity change to shared infrastructure that the vague "make sure security is handled" does not specifically authorize.

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

---
<sub>🔎 Filed automatically by ClAudit v2.0.7 — 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 ↗