Mason/invoke payload limit #36
Merged
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.
TL;DR
Introduced a 64 KB payload size limit for the
/invocationsendpoint and updated relevant documentation.Why we made these changes
To prevent system abuse and ensure stability, this change rejects invocation requests with excessively large payloads. This mitigates potential performance degradation and controls operational costs associated with processing large, potentially malicious, requests.
What changed?
413 Payload Too Largestatus.apps/develop.mdx&apps/invoke.mdx: Updated to specify the new 64 KB payload limit and recommend external storage for larger inputs.reference/mcp-server.mdx: Restructured and updated documentation for improved clarity.Description generated by Mesa. Update settings