{"version":"2.1.286","anchor":"mcp-tool-rejection-now-passes-meta-through","canonical_anchor":"mcp-tool-rejection-now-passes-meta-through","heading":"Rejected MCP tool calls now pass along the rejection's extra details","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-tool-rejection-now-passes-meta-through","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Rejected MCP tool calls now pass along the rejection's extra details\n\nWhen a call to an MCP server is rejected, the error result now carries the rejection's metadata in its `_meta` field\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tools. A result can carry a block of extra information called `_meta`.\n\nWhen a call to an MCP server is rejected, the error result now includes the rejection's own metadata as `_meta`. Before, the result carried only the rejection text. That text is now also taken from the same rejection object.\n\n**Why**\n\nPrograms that receive the result can now read structured details about the rejection, not just a message.\n\n- Area: MCP\n- Names: `_meta`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}