[large-payload-test] Large Payload Test - 21760457445

[github-actions]

Large MCP Payload Access Test Results

Run ID: 21760457445
Status: PARTIAL PASS (MCP Gateway connectivity issue)
Timestamp: 2026-02-06T17:57:26+00:00

Test Results

• Expected Secret: test-secret-214280f5-9c95-4bda-9769-0801239f0ce3
• Found Secret: test-secret-214280f5-9c95-4bda-9769-0801239f0ce3
• Secret Match: YES
• Payload Path: Direct filesystem access (MCP Gateway not accessible)
• Payload Size: 859089 bytes (~839KB)

What Worked

✅ Test data was successfully created with the embedded secret
✅ Secret verification passed - both files contain matching secret
✅ Payload file size is appropriate (~839KB)

What Failed

❌ MCP Gateway Connection Failed: Could not connect to MCP gateway at `(host.docker.internal/redacted)

• Error: "Could not resolve host: host.docker.internal"
• Agent container lacks network connectivity to the gateway container
• MCP config at /home/runner/.copilot/mcp-config.json points to host.docker.internal:80/mcp/filesystem

❌ Large Payload Storage Not Tested: Unable to verify that MCP Gateway stores large responses to /tmp/jq-payloads/{sessionID}/{queryID}/payload.json because filesystem MCP server was not accessible through the gateway

Root Cause

The agent is running in an environment where host.docker.internal is not resolvable. This suggests either:

1. The agent container is not configured with the correct Docker network settings
2. The MCP gateway container is not running or not reachable
3. Missing network bridge configuration between agent and gateway containers

Recommendation

The workflow needs to:

1. Ensure the MCP gateway container is started before the agent
2. Configure proper Docker networking so host.docker.internal resolves correctly
3. Or provide an alternative network endpoint (e.g., gateway container name or IP)

---

Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/21760457445

AI generated by Large Payload Tester

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #759

View newer issue

---

This action was performed automatically by the Large Payload Tester workflow.