{"version":"2.1.246","anchor":"mcp-result-and-blob-writes-go-through-the-storage-layer","canonical_anchor":"mcp-result-and-blob-writes-go-through-the-storage-layer","heading":"MCP result and blob writes go through the storage layer","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/mcp-result-and-blob-writes-go-through-the-storage-layer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### MCP result and blob writes go through the storage layer\n\nOversized MCP results and saved media now write through the storage layer explicitly.\n\n**What**\n\nOversized MCP tool results, binary content blocks, MCP task results and their image and audio saves now pass storage and credential arguments to the file writer instead of relying on defaults, and the task poller carries credentials through its post-restart resume. The saved-output hints you see are unchanged, and the existing kill switch for large output files still applies.\n\n**Evidence**\n\n`[The portion truncated above was not saved: the per-result persist budget is exhausted.]`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}