[Bug][cyber] Safety filter blocked legitimate cloud IAM policy/role configuration work (req_011Ccn3fyJzr74vV5BBGw6tv)

Open 💬 2 comments Opened Jul 7, 2026 by sworrl

Triage: kind cyber · domain cloud-iam · flagging model Sonnet 5 · severity session-halted (blocked authorized work) · reproducible: yes — server-side via the Request ID(s) below

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

Why this is a false positive

The session was performing routine cloud identity and access management configuration — reviewing and adjusting IAM roles, policies, and permission scopes — a standard administrative task with no offensive-security or exploit content involved. The safeguard triggered a full session-ending block on ordinary IAM terminology rather than any harmful request, forcing the user into a manual exemption-application workflow to continue authorized, in-scope work. This is a false positive that disrupts legitimate cloud administration tasks that any IAM practitioner would routinely perform.

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-07-07T04:13:50.368Z.

Request IDs (lookup-able server-side)

  • req_011Ccn3fyJzr74vV5BBGw6tv (2026-07-07T04:13:50.368Z)

In-scope justification

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

Block message

API Error: Sonnet 5's safeguards 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]

Try rephrasing the request in a new session or change your model.

Learn more: https://support.claude.com/en/articles/8106465

Request ID: req_011Ccn3fyJzr74vV5BBGw6tv

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

---
<sub>🔎 Filed automatically by ClAudit v2.0.104 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗