Fix Elicitation by add schema to elicitation requests#1668
Merged
g2vinay merged 2 commits intomicrosoft:mainfrom Feb 9, 2026
Merged
Fix Elicitation by add schema to elicitation requests#1668g2vinay merged 2 commits intomicrosoft:mainfrom
g2vinay merged 2 commits intomicrosoft:mainfrom
Conversation
g2vinay
requested review from
KarishmaGhiya,
alzimmermsft,
Copilot,
hallipr,
msalaman,
sandeep-sen,
weshaggard and
xiangyan99
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Azure MCP server’s sensitive-tool elicitation flow to comply with an MCP SDK breaking change requiring a requestedSchema for form-mode elicitation requests.
Changes:
- Added a changelog entry describing the elicitation schema fix.
- Updated
HandleSecretElicitationAsyncto send an MCP SDKElicitRequestParamsincluding a required basic schema field for confirmation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| servers/Azure.Mcp.Server/changelog-entries/1770433280892.yaml | Documents the bug fix for form-mode elicitation schema requirement. |
| core/Azure.Mcp.Core/src/Areas/Server/Commands/ToolLoading/BaseToolLoader.cs | Adds a basic RequestedSchema to elicitation requests and switches to direct ElicitAsync call/result handling. |
g2vinay
force-pushed
the
fix-elicitation-schema
branch
from
9a0b4de to
c0c4c4c
Compare
- Use simple accept/decline elicitation without form schema for sensitive tools - Fixes error: 'Form mode elicitation requests require a requested schema' - Simpler approach eliminates need to validate form field values - User must explicitly accept or decline the security warning - Ensures compatibility with VS Code and other MCP clients
g2vinay
force-pushed
the
fix-elicitation-schema
branch
from
c0c4c4c to
c926190
Compare
alzimmermsft
approved these changes
Feb 9, 2026
github-project-automation
Bot
moved this from Untriaged
to In Progress
in Azure MCP Server
colbytimm
pushed a commit
to colbytimm/microsoft-mcp
that referenced
this pull request
Apr 20, 2026
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.
MCP SDK released a breaking change, requiring elicitation forms to come with a schema. https://github.com/modelcontextprotocol/csharp-sdk/pull/1151/changes
This PR resolves that issue by adding the schema.