Add cross-links between network.md and MCP network documentation

[Copilot]

Users may not discover that MCP servers have separate network configuration from top-level AI engine network permissions. Added bidirectional links to clarify the two distinct scopes.

Changes

docs/src/content/docs/reference/network.md

• Added "MCP Network Configuration" section explaining container-based MCP servers have separate network config
• Links to MCP Guide's Network Egress Permissions section
• Added MCP Guide to Related Documentation

docs/src/content/docs/guides/mcps.md

• Added note callout in "Network Egress Permissions" section distinguishing MCP-specific config from top-level network permissions
• Links to Network Reference for comprehensive network permission details

Visual Changes

network.md - New section before Related Documentation:

mcps.md - Note callout clarifying separation of concerns:

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /opt/hostedtoolcache/node/24.12.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.12.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro dev (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[plan] Add cross-links between network.md and MCP network documentation</issue_title>
<issue_description>## Objective

Create bidirectional links between the comprehensive network documentation and MCP-specific network configuration to improve discoverability.

Context

Currently:

• docs/src/content/docs/reference/network.md has 200 lines covering top-level network permissions
• MCP network configuration exists but is not cross-linked
• Users may not realize there are two distinct network configurations

Approach

1. Add section to network.md explaining MCP network configuration
2. Link from mcps.md to network.md for context
3. Clarify the scope and purpose of each network configuration type

Files to Modify

• docs/src/content/docs/reference/network.md - Add "MCP Network Configuration" section
• docs/src/content/docs/guides/mcps.md - Add link to network reference

Example Additions

In network.md:

## MCP Network Configuration

Container-based MCP servers have their own network configuration separate from the AI engine. See [MCP Guide](../guides/mcps.md#configuring-network-access) for details.

In mcps.md:

For comprehensive network permission details, see [Network Reference](../reference/network.md).

Acceptance Criteria

• Bidirectional links added between network.md and mcps.md
• Clear explanation of two distinct network configuration scopes
• Links use correct relative paths
• Documentation builds without broken links
  Related to [plan] Address network configuration inconsistencies in MCP tools #8540

AI generated by Plan Command for discussion #8532

Comments on the Issue (you are @copilot in this section)

• Fixes [plan] Add cross-links between network.md and MCP network documentation #8543

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.