server: add maxBodyBytes guard to WebStandardStreamableHTTPServerTransport #1496
+132
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WebStandardStreamableHTTPServerTransport currently falls back to
await req.json()whenparsedBodyis not provided, which reads the full request body with no size guard.This PR adds a
maxBodyBytesoption (default: 1_000_000) and enforces it while parsingapplication/jsonrequest bodies, returning a JSON-RPC error with HTTP 413 when exceeded.req.body.getReader()when availablemaxBodyBytesto0/Infinity@modelcontextprotocol/server