Skip to content

[Bug][aup] Firmware download and analysis of owned drone hardware blocked as policy violation (req_011CcUA5zgQ8m65csGw6oVdS) #71898

Closed as not planned

Description

@sworrl

Triage: kind aup · domain general · severity session-halted (blocked authorized work) · reproducible: yes — server-side via the Request ID(s) below

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

Why this is a false positive

The safety block is a false positive because the conversation involves legitimate firmware analysis of a personally-owned consumer drone — a common interoperability and privacy use case explicitly protected under DMCA Section 1201 exemptions for security research and device owners. The preceding assistant turn had already framed the request as lawful hardware analysis, not exploitation, and the block appears to have triggered on surface-level pattern matching rather than actual harmful intent. No harmful capability was requested or provided: the user sought to examine firmware on hardware they own to restore basic usability after an app ecosystem was restricted.

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-27T17:27:49.470Z.

Request IDs (lookup-able server-side)

  • req_011CcUA5zgQ8m65csGw6oVdS (2026-06-27T17:27:49.470Z)

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.

Request ID: req_011CcU9x4RemnnTJm3r341F2

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

Related reports (same work session, linked)

Distinct false-positive blocks from the same work session, each its own report:
#71849, #71850, #71851, #71856, #71858, #71860, #71861, #71862, #71865, #71866, #71867, #71868, #71871, #71883, #71884, #71885, #71894, #71895, #71896, #71897


🔎 Filed automatically by ClAudit v2.0.85 — a FOSS tool for reporting false-positive Claude Code blocks.

Activity

  1. sworrl commented on Jun 27, 2026

    @sworrl
    Author

    🔗 Related false positive from the same work session: #71899

  2. github-actions commented on Aug 14, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  3. sworrl commented on Aug 14, 2026

    @sworrl
    Author

    Not a duplicate — requesting maintainer reopen. This report covers a distinct incident with its own server-side Request ID; the cited issue is a sibling report from the same work session, intentionally cross-linked by ClAudit. Issue authors can no longer reopen bot-closed issues on this repo, so this close is unrecoverable on our side. (Assessed by ClAudit.)

  4. sworrl commented on Aug 16, 2026

    @sworrl
    Author

    Still relevant. An issue author cannot reopen after a bot close, so this report is tracked with the 2026-08-14 sweep in #86940.

  5. github-actions commented on Oct 4, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  6. locked as resolved and limited conversation to collaborators on Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions