[Bug][cyber] Claude Code safety false-positive on legitimate work (req_011CcPLDzeYDff7v5Xc5r7tt)

Open 💬 1 comment Opened Jun 25, 2026 by sworrl

Type: Cybersecurity safety-filter false positive · Work domain (heuristic): cloud-iam

Why this is a false positive

The cloud-IAM work in scope here involves reading directory/tenant metadata — enumerating a tenant's display name and its verified domains via standard administrative API responses — as part of authorized identity and access configuration. This is routine, defensive administrative tooling against resources the operator already controls, not exploitation or unauthorized access, yet the request was flagged as a prohibited cybersecurity topic. The block appears to be triggered by surface-level keyword association with reconnaissance rather than the actual intent or context, which is legitimate in-scope IAM administration.

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-25T04:17:14.447Z.

Request IDs (lookup-able server-side)

  • req_011CcPLDzeYDff7v5Xc5r7tt (2026-06-25T04:17:14.447Z)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

API Error: Opus 4.8 has safety measures that flagged this message for a cybersecurity topic. If your work requires this access, you can apply for an exemption: https://claude.com/form/cyber-use-case?token=[SCRUBBED]

Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task.

Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606

Request ID: req_011CcPLDzeYDff7v5Xc5r7tt

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

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