Should TLS MITM support come with guardrails to discourage abuse and exploitation?

We support a TLS MITM in the browser in order to relay native HTTP requests to the browser's Fetch API. Some questions:

- What dangers are there for abuse?
- How can we discourage abuse?
- How can we design the default path so users are not easily exploitable by default?

The issue names no files or tests. Start by reviewing the existing browser TLS MITM path that relays native HTTP requests to the Fetch API, then identify abuse risks, trust boundaries, and unsafe defaults. Done means maintainers agree on guardrails, a safer default path, and an implementation plan.

Written by the indexing model from the issue text.