Enforce AWF firewall on MCP sibling containers to prevent docker exec bypass #10329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MCP Gateway spawns sibling containers (safe-outputs, etc.) via Docker socket without inheriting proxy settings from AWF, allowing unrestricted network access via
docker exec.Changes
MCP Gateway container (
pkg/workflow/mcp_servers.go)HTTP_PROXY,HTTPS_PROXY,http_proxy,https_proxy,NO_PROXY,no_proxy) to gateway container via-eflagsSafe-outputs container config (
pkg/workflow/mcp-config.go,pkg/workflow/mcp_renderer.go)envconfiguration (JSON format for Copilot/Claude)env_varslist (TOML format for Codex)Flow
Commands executed inside safe-outputs container now respect firewall rules, including those run via
docker exec.Related: githubnext/gh-aw-firewall#130
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.