feat: enforce greet(name) input bounds via pydantic.Field#19
Merged
Conversation
Audit (2026-05-01, P2.16): the TS sibling validates greet's name with Zod (1–200 chars). Python equivalent was untyped — empty strings and megastring inputs reached the handler. Switch the parameter annotation from `name: str` to `name: Annotated[str, Field(min_length=1, max_length=200, description=...)]`. FastMCP picks up the Annotated metadata and emits the constraint into the tool's JSON schema, so violations are rejected at protocol level. Tests pass; mypy strict still clean.
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.
From the 2026-05-01 audit (P2.16). Restores parity with the TS sibling's Zod constraint.
Switch from bare
name: strto:FastMCP propagates the
Fieldmetadata into the JSON schema; protocol layer rejects empty / oversized inputs before the handler runs.Test plan