api-mitmproxy

Purpose and capabilities are internally consistent: this is an official-tool guide for mitmproxy-based API interception and testing, not a disguised credential harvester. However, it is inherently high risk because it gives an AI agent offensive traffic interception, modification, replay, token capture, and SSL-unpinning workflows; use should be limited to authorized security testing environments.

The content presents high supply-chain and operational security risk primarily due to CI behaviors: a remote installer is piped directly into Bash (unverified remote code execution during CI), and a repository token is provided to third-party actions referenced via mutable/tag-based resolution (amplifying impact of upstream compromise). Additionally, the documentation/examples include risky credential handling (logging Authorization token prefixes) and a destructive cleanup command (rm -rf ~/.mitmproxy/) that can destroy interception trust material and configuration. Overall risk is high for CI environments and should be remediated by removing pipe-to-shell installs, pinning actions/versions, verifying downloads, and tightening logging/cleanup guidance.