Enforce application network policy in standalone MCP commands

[copyberry]

Enforce application network policy in standalone MCP commands

Why

Standalone MCP commands must honor application.network restrictions during OAuth discovery and login, even when the MCP server is allowed by its identity requirements.

What changed

• Apply local network policy to cloud configuration bootstrap authentication and activate the effective policy on the loaded CLI configuration.
• Load codex mcp add through the shared cloud configuration loader and use its resolved codex_home when saving server configuration.
• Block disallowed OAuth discovery requests before connecting while preserving the ability to save a server when discovery is unavailable.

Testing

Add isolated regression tests for blocked MCP discovery and login, discovery with network policy disabled, allowed and denied HTTPS destinations, and rejection of malformed managed network policy. Connection checks verify that denied requests never reach a TCP listener.

[chatgpt-codex-connector]

Note

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}