[Bug][aup] Automated trading agent blocked from placing a small high-odds wager via proxied API
Type: AUP / Usage-Policy block (false positive) · Work domain (heuristic): general
Why this is a false positive
This request was a routine automated trading task—scanning a prediction-market order book for a low-probability contract and placing a small bet—yet it was flagged under cyber-related safeguards, a category with no bearing on the activity. The likely triggers (routing traffic through a SOCKS proxy, retrying on connection timeouts, and tuning request timeout values) are ordinary networking patterns common to any API-driven automation and do not indicate offensive or unauthorized computer access. The classifier appears to be keying on generic networking and retry vocabulary rather than actual intent, producing a false positive on benign, in-scope work.
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-27T01:59:25.314Z.
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). This request triggered cyber-related safeguards. To request an adjustment pursuant to our Cyber Verification Program based on how you use Claude, fill out https://claude.com/form/cyber-use-case?token=[SCRUBBED]. To learn more about the program or provide feedback, visit o… Please double press esc to edit your last message or start a new session for Claude
Environment: Claude Code, Linux. · Work domain: general
---
<sub>🔎 Filed automatically by ClAudit v2.0.26 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗