MCP read-only hint trust tier approval behavior
Cluster 121042. Data as of
Nothing open on GitHub. Fix merged in #133532 on 5 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #133532. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items relate to how read-only hints (readOnlyHint/snake_case variants) are recognized for MCP tools on untrusted servers, affecting whether approval prompts are required. The work involves a bug report and related fix attempts around MCP 2.x compatibility with this hint.
Open issues0
Open PRs0
Fixes on record
-
#133532 MCP read-only tools on untrusted servers stop asking for approval under mcp 2.x (salvage #111270)
files:
contributors/emails/[redacted:email],tests/e2e/core/mcp_plugins/test_mcp_stdio_conformance.py,tests/tools/test_mcp_trust_gating.py,tools/mcp_tool_registration.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#121044 fix(mcp): honor snake case read-only hints · done elsewhere →
4b6884a,#133532,#111270,#88372
Closed issues · 1
- Closed#121042MCP trust tier can't see readOnlyHint with mcp 2.0.0 — every tool on a trust: untrusted server requires approval
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #133532
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 5 Oct 2026