{"version":"2.1.314","anchor":"mcp-tool-task-results-validate-base64","canonical_anchor":"mcp-tool-task-results-validate-base64","heading":"Damaged images and files from MCP tasks are no longer saved","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-tool-task-results-validate-base64","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Damaged images and files from MCP tasks are no longer saved\n\nClaude Code now checks images and files returned by MCP tasks and skips saving any that arrive damaged, with a message saying so\n\n**What**\n\nAn MCP server is an outside tool server Claude Code connects to. Its tasks can return images and files sent as base64, a way of writing binary data as plain text. Claude Code now checks that this data decodes properly before saving it. If it does not, nothing is saved and you see: \"content not saved: the server sent data that is not valid base64\".\n\n**Why**\n\nA misbehaving MCP server can no longer leave corrupt files behind.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}