Operations: Loopback Policy Violations
This page describes diagnosis/remediation when local-only policy is violated.What Violates Policy
- binding ClawControl to non-loopback interfaces
- attempting to expose via
tailscale serve - reverse proxy/public tunnel exposure
Detection
403response from proxy host guard for non-loopback host headers- startup guard failure from local-only script
- listener checks showing
0.0.0.0instead of loopback
Verification Commands
127.0.0.1 and/or ::1 only.
Required Remediation
- remove non-loopback host env overrides
- stop unsupported exposure tooling
- restart ClawControl in local-only mode
- use SSH tunnel workflow for remote operations