[Bug][harness] Safety block halts authorized printer-driver/feature-enable troubleshooting on a production RDS

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

Why this is a false positive

The block fires on a printer-installation troubleshooting flow that legitimately needs -ExecutionPolicy Bypass and a scheduled task only because the session-0 / interactive-context restrictions on a remote shell prevent the printer driver and optional feature from registering directly — there is no persistence objective, just a standard workaround for installing a device on a server without an interactive desktop session. The "don't reboot" instruction is a narrowing constraint within already-authorized administrative remote-management work, not the sole grant of authority, so treating it as the only boundary and inferring "Unauthorized Persistence / Security Weaken" mischaracterizes scoped IT administration as an attack. The execution-policy flag and onlogon trigger are conventional, non-evasive techniques used here for their documented operational purpose, not to weaken security or evade detection.

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-20T05:32:44.062Z.

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

Creates a persistent onlogon scheduled task with -ExecutionPolicy Bypass on shared production server [REDACTED]-[REDACTED] via remote shell — Unauthorized Persistence and Security Weaken not explicitly authorized by the user, who only set a "don't reboot" boundary.

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

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