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

[github-actions]

Large MCP Payload Access Test Results

Run ID: 21762627709
Status: PARTIAL PASS
Timestamp: 2026-02-06T19:10:21Z

Test Results

• Expected Secret: test-secret-2786167c-221f-4a0f-a034-f88ef8394279
• Found Secret: test-secret-2786167c-221f-4a0f-a034-f88ef8394279
• Secret Match: YES ✅
• Payload Path: NOT PROVIDED (feature not triggered)
• Payload Size: 672,508 bytes (656.7 KB)

Detailed Findings

✅ What Worked

1. Successfully read secret.txt from filesystem MCP server
2. Successfully read large-test-file.json (672KB file)
3. Secret validation passed - secrets match correctly
4. File content integrity verified

⚠️ What Failed

1. Large payload storage not triggered: Despite 672KB response, MCP Gateway did not store payload to /tmp/jq-payloads/{sessionID}/{queryID}/payload.json
2. No payload metadata returned: Response did not include payloadPath, queryID, or other expected metadata fields
3. No stored payload files found: Search for payload.json files in /tmp returned no results

Conclusion

The filesystem MCP server is functioning correctly and can read large files. Secret verification passed. However, the MCP Gateway's large payload storage feature is not being activated despite the response size (672KB) exceeding typical thresholds. The gateway appears to be passing through the full content directly rather than storing it and returning metadata.

This suggests either:

• The jq middleware is not enabled/configured correctly
• The payload size threshold is set higher than 672KB
• The feature is not triggered for filesystem MCP server responses

---

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

AI generated by Large Payload Tester