Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Tooling ArchitectureArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
Unclear The finding doesn't say which specific tool this exception applies to.
What
The internal logic that classifies a tool as MCP (Model Context Protocol), built-in, or undefined now takes an extra input and adds a special case: if a tool's name matches one particular built-in tool and none of the extra input matches a specific identifier, it's classified as "built-in" even in a situation where it would otherwise have failed the general built-in check.
Why
This fixes a case where that particular tool could be misclassified, ensuring it's consistently recognized as a built-in tool.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding doesn't say which specific tool this exception applies to.
