Use current MCP authority for elicitation reviews - #35205
Merged
copyberry[bot] merged 1 commit intoJul 24, 2026
Merged
Conversation
## Why MCP elicitation reviewers are reused across runtime refreshes, while an active turn can retain the approval settings it started with. Reviewing against that turn could therefore apply stale authority after session settings changed. ## What changed - Read the latest published MCP runtime configuration when reviewing an elicitation, including the approval policy, permission profile, configuration layers, and reviewer selection. - Apply `never` and granular MCP-elicitation policy decisions before routing an eligible request to Guardian. - Keep MCP runtime startup registered for refresh invalidation through session creation. ## Testing Added coverage that refreshes a running session and verifies the same reviewer uses the latest authority for Guardian routing, denial, and empty-form auto-approval. GitOrigin-RevId: 826a157aa70fc8e3a9e3a14ecb0261bf7b63f63a
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/826a157aa70fc8e3a9e3a14ecb0261bf7b63f63a
branch
from
July 24, 2026 15:17
6ef58e9 to
000d254
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/826a157aa70fc8e3a9e3a14ecb0261bf7b63f63a
branch
July 24, 2026 15:18
cryptomasters
temporarily deployed
to
issue-triage
July 24, 2026 15:45 — with 
GitHub Actions
Inactive
cryptomasters
temporarily deployed
to
issue-triage
July 24, 2026 15:45 — with
GitHub Actions
Inactive
cryptomasters
temporarily deployed
to
issue-triage
July 24, 2026 15:45 — with
GitHub Actions
Inactive
BetterPlacesLibrary
temporarily deployed
to
issue-triage
July 24, 2026 16:22 — with
GitHub Actions
Inactive
BetterPlacesLibrary
temporarily deployed
to
issue-triage
July 24, 2026 16:22 — with
GitHub Actions
Inactive
BetterPlacesLibrary
temporarily deployed
to
issue-triage
July 24, 2026 16:23 — with
GitHub Actions
Inactive
BetterPlacesLibrary
temporarily deployed
to
issue-triage
July 24, 2026 16:24 — with
GitHub Actions
Inactive
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
9 participants
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.
Use current MCP authority for elicitation reviews
Why
MCP elicitation reviewers are reused across runtime refreshes, while an active
turn can retain the approval settings it started with. Reviewing against that
turn could therefore apply stale authority after session settings changed.
What changed
elicitation, including the approval policy, permission profile, configuration
layers, and reviewer selection.
neverand granular MCP-elicitation policy decisions before routing aneligible request to Guardian.
creation.
Testing
Added coverage that refreshes a running session and verifies the same reviewer
uses the latest authority for Guardian routing, denial, and empty-form
auto-approval.