[Bug][cyber] Safety block stopped read-only IR mailbox triage and credential lockdown via Graph API in authori (req_011CcPK7qhVF6zoCygQv6LWY)

Open 💬 2 comments Opened Jun 25, 2026 by sworrl

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

Why this is a false positive

The cybersecurity-topic filter triggered on a routine cloud-IAM administrative task — auditing and securing a set of email accounts within an organization's own tenant, in response to a suspected business-email-compromise incident, using application credentials the account owner explicitly authorized. This is standard defensive incident-response and identity-hardening work performed by an administrator on infrastructure they control, not offensive activity, intrusion, or access to any third-party system. The block prevents legitimate, in-scope remediation and should be treated as a false positive.

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:02:50.987Z.

Request IDs (lookup-able server-side)

  • req_011CcPK7qhVF6zoCygQv6LWY (2026-06-25T04:02:50.987Z)

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_011CcPK7qhVF6zoCygQv6LWY

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

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