Large MCP Payload Access Test Results
Run ID: 24405792294
Status: FAIL
Timestamp: 2026-04-14T14:50:13Z
Test Results
- Expected Secret:
test-secret-4cacc371-d641-42a8-a871-b44a45e69182
- Found Secret:
test-secret-4cacc371-d641-42a8-a871-b44a45e69182 (read directly from disk — NOT via MCP)
- Secret Match: YES (data integrity OK, but verified via bash, not MCP)
- Payload Path: NOT OBTAINED — filesystem MCP tools were unavailable to the agent
- Payload Size: 780,579 bytes (~763 KB, above 512 KB default threshold)
Failure Analysis
The filesystem MCP server was running (/health confirmed filesystem: status: running, uptime: 239s), and the copilot agent successfully connected to the gateway at `(host.docker.internal/redacted)
However, the filesystem MCP tools were never registered with the agent:
- Agent logs show:
Loading tools for client: filesystem (no errors)
- But no
filesystem-* tools appear in the Adding tool: log entries
- Only
github-* and safeoutputs-* tools were registered
Root cause: The workflow tools: allowlist only includes github (toolsets) and bash. The filesystem MCP server is not listed, so its tools are filtered out and not exposed to the agent. As a result:
- The agent could not call
filesystem/read_file or any filesystem MCP tool
- No large payload was routed through the gateway
- The MCP payloads directory (
/tmp/gh-aw/mcp-payloads/) remained empty
- The payloadPath large-payload flow was never exercised
Conclusion
The large payload access mechanism could not be tested end-to-end. The filesystem MCP server is healthy and the data is intact (secrets match when read directly), but the agent was blocked from using filesystem MCP tools due to the tools allowlist configuration in the workflow YAML. The tools: section needs to include a filesystem: entry (or the allowlist needs to permit filesystem server tools) for this test to work as designed.
Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/24405792294
Generated by Large Payload Tester · ● 1.4M · ◷
Large MCP Payload Access Test Results
Run ID: 24405792294
Status: FAIL
Timestamp: 2026-04-14T14:50:13Z
Test Results
test-secret-4cacc371-d641-42a8-a871-b44a45e69182test-secret-4cacc371-d641-42a8-a871-b44a45e69182(read directly from disk — NOT via MCP)Failure Analysis
The filesystem MCP server was running (
/healthconfirmedfilesystem: status: running, uptime: 239s), and the copilot agent successfully connected to the gateway at `(host.docker.internal/redacted)However, the filesystem MCP tools were never registered with the agent:
Loading tools for client: filesystem(no errors)filesystem-*tools appear in theAdding tool:log entriesgithub-*andsafeoutputs-*tools were registeredRoot cause: The workflow
tools:allowlist only includesgithub(toolsets) andbash. ThefilesystemMCP server is not listed, so its tools are filtered out and not exposed to the agent. As a result:filesystem/read_fileor any filesystem MCP tool/tmp/gh-aw/mcp-payloads/) remained emptyConclusion
The large payload access mechanism could not be tested end-to-end. The filesystem MCP server is healthy and the data is intact (secrets match when read directly), but the agent was blocked from using filesystem MCP tools due to the tools allowlist configuration in the workflow YAML. The
tools:section needs to include afilesystem:entry (or the allowlist needs to permit filesystem server tools) for this test to work as designed.Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/24405792294