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

[github-actions]

Large MCP Payload Access Test Results

Run ID: 21732761284
Status: INCOMPLETE - Tool Access Issue
Timestamp: 2026-02-05T23:40:07Z

Test Results

1. ✅ Read test secret from control file
2. ❌ Trigger large payload response (>1KB) - Cannot access MCP tools
3. ❌ Receive gateway metadata with payloadPath - Cannot access MCP tools
4. ❌ Translate and access payload file path - Cannot access MCP tools
5. ❌ Read payload file contents - Cannot access MCP tools
6. ❌ Extract and verify secret - Cannot access MCP tools

Details

• Expected Secret: test-secret-ef7c61a6-92d2-4de4-ba78-1bbd1b86f998
• Found Secret: NOT FOUND - Test could not proceed
• Secret Match: N/A
• Gateway Path: N/A - Tool invocation failed
• Agent Path: N/A - Test did not reach this step
• Payload Size: N/A
• Query ID: N/A

Partial Verification Completed

✅ Test Environment Setup Verified:

• Test data directory exists: /tmp/mcp-test-fs/
• Secret file exists and contains: test-secret-ef7c61a6-92d2-4de4-ba78-1bbd1b86f998
• Large test file exists: /tmp/mcp-test-fs/large-test-file.json (859,158 bytes / ~838KB)
• Files are accessible from runner filesystem

❌ MCP Tool Access Issue:

• MCP configuration found at: /home/runner/.copilot/mcp-config.json
• Filesystem MCP server configured with endpoint: `(host.docker.internal/redacted)
• Gateway endpoint is not accessible from agent context (DNS resolution fails for host.docker.internal)
• No mechanism available to invoke MCP read_file tool from agent environment
• Cannot test the actual large payload storage/retrieval flow

Root Cause

The test agent does not have a working mechanism to invoke MCP tools. The workflow expects the agent to:

1. Call filesystem.read_file to trigger a large response
2. Receive gateway-intercepted metadata with payloadPath
3. Read the stored payload file

However:

• The gh mcp command does not exist
• The MCP HTTP endpoints are not accessible from the runner (DNS fails for host.docker.internal)
• No alternative tool invocation mechanism is apparent in this environment

Recommendations

1. Verify MCP Gateway is Running: Ensure the gateway container is launched and accessible before agent execution
2. Fix DNS/Networking: The host.docker.internal hostname should resolve to the gateway
3. Tool Access Method: Provide a clear mechanism for agents to invoke MCP tools (e.g., gh-mcp, HTTP client, or built-in function)
4. Documentation: Update workflow docs with how agents should invoke MCP tools in the Agentic Workflows environment

Conclusion

Test environment setup is correct, but the test cannot proceed due to missing tool access. The large payload storage feature cannot be validated without the ability to trigger MCP tool calls that generate large responses.

---

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

AI generated by Large Payload Tester

[github-actions]

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

View newer issue

---

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