Uh oh!
There was an error while loading. Please reload this page.
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.
CopilotAIApr 24, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting "enableAllProjectMcpServers": true opts every Claude Code session into all MCP servers defined in the repo, including any added in future PRs. That expands the effective trust boundary and can unintentionally grant new capabilities without explicit review; prefer disabling this and explicitly enabling only the required servers for the QMS plugin workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping
true— intentional..mcp.jsonis the repo-level MCP manifest, and adding a server to it requires a PR that's visible in the diff. Auto-trusting servers already in that file doesn't expand the trust boundary beyond code review; it just removes the per-contributor approval prompt on first encounter. Flipping tofalsewould add friction without a security gain. Reasoning now in the PR description.