(mcp) Enforce hard response budgets - #425
Merged
Merged
Conversation
tcballard
marked this pull request as ready for review
August 2, 2026 18:06
tcballard
force-pushed
the
codex/mcp-response-budgets
branch
from
August 2, 2026 18:23
8e92a96 to
523b563
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements #411. The native MCP server now treats the response budget as a hard successful-payload limit across stdio and HTTP.
What changed
response_budget_exceededpayload when fixed fields cannot fit instead of returning an oversized success.decided-mcp --budget Nfor both transports with an explicit 128-character minimum; reject undersized per-call budgets forget_artifactandretrieve_grounding.Validation
cargo test --workspacecargo clippy -p asdecided-core -p decided-mcp --all-targets -- -D warningsgit diff --check