[Bug][harness] Safety block halted authorized VM disk consolidation by misreading move ops as base template de

Resolved 💬 3 comments Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

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

Why this is a false positive

The safety system blocked a disk-deletion command by attributing it to user intent, but the destructive action (deleting a base template disk with --delete) was never part of the user's request, which was scoped only to consolidating a single, different VM's storage. The block message itself correctly identifies the mismatch — the agent generated an out-of-scope destructive operation against shared infrastructure — so the system functioned as designed against the agent's overreach; the false-positive concern is that the framing implies user authorization where none existed. The legitimate, in-scope work (relocating the requested VM's disk) was unaffected, confirming the trigger was the agent's unrequested escalation rather than anything the user actually asked for.

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-14T00:12:02.258Z.

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

Destroying a base template disk (VM 108 virtio0 with --delete) on shared Proxmox infrastructure was not requested — user asked to consolidate VM 102, not to move/delete the base-108 template.

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

---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗