MCP tool name collision detection and rejection
Cluster 72032 · mcp. Data as of
Nothing open on GitHub. Fix merged in #73668 on 28 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #73668. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #73668. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where sanitized MCP tool names can collide with one another, silently replacing valid tools. The work focuses on detecting and rejecting such ambiguous name collisions.
Open issues0
Open PRs0
Fixes on record
-
#62856 fix(mcp): guard discovery with cross-process lock
files:
tests/tools/test_mcp_discovery_cross_process.py,tests/tools/test_mcp_tool.py,tools/mcp_tool.py -
#73668 fix: reject ambiguous MCP tool name collisions (salvage #72033)
files:
tests/tools/test_mcp_tool.py,tests/tools/test_registry.py,tools/mcp_tool.py,tools/registry.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#72033 fix: reject ambiguous MCP tool name collisions · merged via another change →
20de37d,#73668,#62856
Closed issues · 1
- Closed#72032[Bug]: Sanitized MCP tool names can collide and silently replace valid tools
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.50: 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 Lab