Skip to content

[awf] squid-config: topologyAttach MCP gateway hostname not added to Squid ACL allowlist #6652

Description

@lpcox

Problem

The AWF firewall blocks the internal MCP gateway (awmg-mcpg:8080) at runtime. The block report then recommends adding awmgmcpg to network.allowed, but that hostname fails schema validation in the compiler. There is no documented or working way to allow this internal hop.

Context

Original report: github/gh-aw#45915

Root Cause

The MCP gateway is declared under topologyAttach in the compiled lock file, but AWF's Squid ACL is not automatically populated with that hostname. The topologyAttach mechanism sets up network routing but does not inject the gateway hostname into the Squid domain allowlist. As a result, CONNECT awmg-mcpg:8080 is denied by Squid's default-deny policy.

Proposed Solution

In src/squid-config.ts (generateSquidConfig()), when topologyAttach entries are present, automatically add their hostnames to the Squid ACL allowed_domains list. Alternatively, in src/docker-manager.ts, detect topologyAttach entries and pass them as additional --allow-domains entries so they bypass Squid filtering. The gateway should never appear in user-facing block reports.

Generated by Firewall Issue Dispatcher · sonnet46 · 30.4 AIC · ⊞ 6.4K ·

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions