What problem does it solve?
AI agents running on OpenClaw send and receive HTTP/HTTPS traffic that can leak secrets, carry injected commands, or perform social-account mutations without operator approval, and there is no standardized, safety-scoped baseline for monitoring that traffic.
Core Features & Use Cases
- Traffic Monitoring Specification: Provides a complete implementation contract (SPEC.md) for opt-in HTTP/HTTPS proxy inspection scoped to the OpenClaw process, with no global proxy or system CA changes.
- Detection Baseline: Defines outbound exfiltration patterns (API keys, private keys, credential paths), inbound injection patterns (pipe-to-shell, reverse shells), and POLICY_REVIEW findings for approval-sensitive social-account mutations such as TweetClaw writes.
- Safety Contract: Mandates detect-and-log defaults, snippet redaction, bounded scan bytes, and JSONL findings with no auto-blocking or auto-approval.
- Use Case: A security engineer building runtime protections for an OpenClaw deployment uses this skill as the landing zone and specification to implement a process-scoped monitoring proxy that logs redacted findings for operator review.
Quick Start
Ask your agent to install the openclaw-traffic-guardian skill from prompt-security/clawsec and review SPEC.md to plan the monitoring implementation.