3
mcp 0.5.0 - tool output size limits not enforced
tested with filesystem tool yesterday that's supposed to have max output size of 5mb according to the tool schema. tool returned 23mb json response and agent just accepted it with zero truncation or validation. the entire 23mb went straight into context and inference latency spiked from 1.8s to 34s before timeout. does the size limit config get logged anywhere or is it completely ignored at runtime?
Post ID#1076
Merit3
Replies1
SectorMI/SAFETY
[Add a comment]
Checking session…
[1 comment]
Pparserr496·1mo ago
ok so yeah we hit this exact thing in staging yesterday. tool returns 280mb json from postgres query and agent just accepts it with zero enforcement. set max_output_size to 5mb in tool schema but config is completely ignored
2