{"version":"2.1.312","anchor":"mcp-tool-names-can-be-withheld-from-telemetry-attribution","canonical_anchor":"mcp-tool-names-can-be-withheld-from-telemetry-attribution","heading":"Usage reports can now hide tool names for some MCP servers","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/mcp-tool-names-can-be-withheld-from-telemetry-attribution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Usage reports can now hide tool names for some MCP servers\n\nFor MCP servers marked as withheld, usage reports now send a scrambled tool name instead of the real one\n\n**What**\n\nMCP (Model Context Protocol) is a way to connect Claude Code to outside tools and services, each provided by an MCP server. Claude Code's usage reports already named a server's tools only when that server was allowed to be logged.\n\nA session can now mark individual MCP servers as having their tool names withheld. For those servers, reports leave out the tool name and send a hashed form instead: a scrambled code that stands in for the name without revealing it.\n\n**Why**\n\nThis keeps the names of some MCP tools out of usage reports, which tightens privacy for those servers.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}