You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[deep-report] Daily Go Test Parallelizer bypasses GitHub MCP proxy, causing 75% of fleet firewall blocks #58847
The 2026-09-05 Daily Security Observability Report (#58836) shows api.github.com:443 accounted for 235 of 314 total blocked requests fleet-wide (75%) over the last 7 days, almost entirely attributed to Daily Go Test Parallelizer and PR Sous Chef. The same workflow also appears across 6 of the 9 blocked-domain rows this cycle (api.github.com, ab.chatgpt.com, github.com, pypi.org, cafe.github.com, raw.githubusercontent.com) and shows a 0/1 hard failure in today's Agent Performance Report (#58814), consistent with this workflow's previously-tracked chronic low success rate (~15-20% in earlier cycles per repo-memory). This pattern is consistent with the workflow (or a script/tool it invokes) making direct GitHub API/git calls outside the intended GitHub MCP tool proxy or declared network.allowed list, rather than a misconfigured allowlist for legitimate traffic.
Note: this cycle's sandbox could not read .github/workflows/daily-go-test-parallelizer.md directly (an MCP get_file_contents secrecy-policy filter blocked the read) — the fix owner should inspect that file's tools/network frontmatter and any embedded scripts directly.
Expected Impact
Eliminating the direct API bypass should reduce fleet-wide firewall block volume by roughly 75% and may resolve or clarify this workflow's chronic failure rate, since blocked outbound calls are a plausible root cause of its low success.
Suggested Agent
Daily Security Observability Report / manual maintainer review of .github/workflows/daily-go-test-parallelizer.md
Activity