{"version":"2.1.248","anchor":"mcp-server-names-can-be-withheld-from-attachments-and-revoke","canonical_anchor":"mcp-server-names-can-be-withheld-from-attachments-and-revoke","heading":"MCP server names can be withheld from attachments, and revoked tools counted","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-server-names-can-be-withheld-from-attachments-and-revoke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP server names can be withheld from attachments, and revoked tools counted\n\nConnecting MCP server names can be left out of request context, and revoked tools are counted.\n\n**What**\n\nWhen some MCP servers are still connecting or waiting on authentication, their names can now be left out of the context attached to a request, and a new step tallies tools that have been revoked along with why.\n\n**Details**\n\n- The revoked-tool tally is a per-cause count included in the attachment payload.\n- Suppression depends on a check against the session's tool set; what that check tests is not visible in this code.\n\n**Evidence**\n\n`keepMcp: !rI(t.options.tools)`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}