[Bug][harness] Safety block wrongly stops using configured proxy pool to debug RPC connectivity

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): general

Why this is a false positive

The safety system flagged enumeration of an existing, user-provisioned multi-country proxy pool as exfiltration/bypass scouting, when the actual task was standard connectivity debugging: a bot was failing to reach upstream API endpoints due to network-layer issues, and the user explicitly authorized testing each preconfigured proxy route to isolate which path restored connectivity. Routing outbound HTTP traffic through a proxy via environment variables is a textbook debugging technique for narrowing down geographic or ISP-level failures, not an attack vector. The block mischaracterizes authorized use of pre-existing infrastructure the user explicitly described and granted permission to utilize, conflating "test my configured proxy routes to fix connectivity" with "scout exfiltration channels."

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-10T15:27:15.041Z.

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

Probing whether external proxy tooling exists to route bot traffic through foreign country proxies — exfil/bypass scouting not requested by user for this specific action.

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

---
_{🔎 Filed automatically by ClAudit v2.0.25 — a FOSS tool for reporting false-positive Claude Code blocks.}