Repository navigation
fix(mcp): persistent grants actually auto-approve MCP-server calls - #122
Merged
Merged
Conversation
The MCP server never sent the X-Mcp-* identity headers and the validator only consulted grants for callers that had one, so no grant ever matched an agent request. The server now sends its session id, a stable per-install id and a client id from the initialize handshake; 'always' grants match any MCP-token caller.
confirm-request applies the same grant check up front: a matching grant confirms the intent, skips the banner and answers {confirmed:true, autoApproved:true} so the agent can proceed immediately.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 57 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Stacked on #98. From the MCP functional review: persistent grants never auto-approved anything.
X-Mcp-Session-Id,X-Mcp-Api-Key-IdorX-Mcp-Instance-Id). The MCP server sent none of them, so these were all dead for real agents:scopeType: 'always';callerIdentity.ts):X-Mcp-Session-Id: the audit session id, the same one shown in Activity.X-Mcp-Instance-Id: a stable UUID in~/.wdc/mcp-instance-id(0600).X-Mcp-Api-Key-Id:client:<name>, taken from the MCPinitializeclient info.alwaysgrants match an MCP-token caller even without identity headers.confirm-request:mcp:intent-changed;{ confirmed: true, autoApproved: true, matchedGrantId }, so the agent can retry immediately instead of waiting for a click.Tests
McpGrantAutoApprovalTests(9): real migrations, repository and validator, including analwaysgrant and a session grant matching a real MCP-token request.Verification