[Bug][aup] Defensive admin API-key proxy hardening task blocked mid-implementation after handler tests passed

Type: AUP / Usage-Policy block (false positive) · Work domain (heuristic): defensive-hardening

Why this is a false positive

This was legitimate defensive-hardening work: the assistant was implementing and testing an admin key-management proxy feature, writing handler tests, and building a binary—all standard authenticated application development. The refusal triggered mid-task on a routine continuation step ("what hardening work remains"), with no request for an exploit, attack technique, or any disallowed capability. The block appears to be a false positive driven by surface-level security keywords ("keys," "hardening," "proxy") rather than any actual policy-violating intent in the conversation.

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-05-21T17:36:28.767Z.

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

API Error: Claude Code is unable to respond to this request, which appears to violate our Usage Policy (https://www.anthropic.com/legal/aup). Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task. If you are seeing this refusal repeatedly, try running /model claude-sonnet-4-20250514 to switch models.

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

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