[Bug][harness] SSH port-forward on hypervisor for service relay wrongly blocked as unauthorized

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

Why this is a false positive

The block misidentifies the hypervisor network change as out-of-scope when it was the direct, minimum-necessary step to achieve an explicitly authorized goal: connecting a VM to a relay that was unreachable due to a VLAN access restriction. Configuring a port-forward or bridge IP on the hypervisor host is standard infrastructure remediation for a connectivity problem, not an independent lateral action on shared resources. The safety heuristic incorrectly anchored scope to only one sub-task (GUI wiring) while ignoring the broader session context in which relay connectivity for that same service was an active, user-directed workstream.

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-10T23:57:01.144Z.

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

Adding an IP to a VLAN bridge on the shared Proxmox host via SSH is a Remote Shell Write / Modify Shared Resources action on shared infrastructure that the user never authorized — the user asked for GUI wiring in [REDACTED], not Proxmox network reconfiguration.

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

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