Repository navigation
fix(server): reject Mcp-Param values the header check cannot verify - #3167
Conversation
🦋 Changeset detectedLatest commit: 45c03c9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
An object or array body value for an x-mcp-header argument is now rejected whether or not its header is present. Leaving the no-header case to params validation was not safe: a coercing schema such as z.coerce.string() turns ["eu"] into "eu", so the tool ran with a value no header carried. An integer outside the safe range has no header form. A present header cannot be compared with it, so it is rejected; an absent header is still accepted, because the SDK's own client omits the header for such values.
mattzcarey
changed the title
| '@modelcontextprotocol/server': patch | ||
| --- | ||
|
|
||
| Reject a `tools/call` with `400` / `-32020` (`HeaderMismatch`) when a body argument declared with `x-mcp-header` is an object or array, with or without its `Mcp-Param-*` header, and when the argument is an integer outside the safe range but the header is present. Previously the header check was skipped for these values, so the call reached the tool. |
There was a problem hiding this comment.
🟡 nit (optional): Release-note readers are told these calls used to reach the tool, but for most tools they were answered 200 with a tool input-validation error. The last sentence of the changeset at line 6 holds only when the tool's validator accepts the value, such as z.coerce.string() given an array. Fix: state what callers see change in both cases: a call that got 200 with an isError input-validation result, or that ran the tool under a coercing schema, now gets 400 / -32020.
Why this was flagged
No runtime trigger; nothing fails at runtime, the reader of the published changelog is the one affected. .changeset/mcp-param-header-non-primitive-body.md:6 ends "Previously the header check was skipped for these values, so the call reached the tool." On the base branch an object or array for a declared argument skipped the header check, then validateToolInput at packages/server/src/server/mcp.ts:370-375 threw "Input validation error: Invalid arguments for tool ...", and the catch at packages/server/src/server/mcp.ts:320 returned it as an isError result with HTTP 200. executeToolHandler at packages/server/src/server/mcp.ts:307 never ran. The tool ran only when the schema's own validator accepted the value, for example a coercing schema, or a JSON Schema integer for a value outside the safe range. The instruction guards against release notes that understate a visible change: here a 200 tool error becomes a 400 protocol error for every tool, not only coercing ones.
Verification: The changeset's last sentence (.changeset/mcp-param-header-non-primitive-body.md:6) reads: "Previously the header check was skipped for these values, so the call reached the tool." So the caller-visible change for the common case is 200 with an isError input-validation result becoming 400 / -32020; the tool handler never ran.
Finding ID: f-a963bbc4
claude
Bot
added
the
v2
No description provided.