{"version":"2.1.307","anchor":"mcp-file-reference-approval-can-show-the-file-content","canonical_anchor":"mcp-file-reference-approval-can-show-the-file-content","heading":"Approving an MCP file upload can now show the file's actual content","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-file-reference-approval-can-show-the-file-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Approving an MCP file upload can now show the file's actual content\n\nWith approvalSeesContent, MCP file-reference tools read the file up front so your approval and the auto-classifier see what is being sent\n\n**What**\n\nSome MCP tools (tools provided by outside services, such as uploading a file to Drive) take a reference to a file on your computer. Before, only that reference was held when you were asked to approve the call, and the file was read later when it was sent. A tool can now be configured with `approvalSeesContent`:\n\n- The file is read when the call is checked, and its content is filled in (base64 encoded, a text form of the file) so the approval prompt and the auto-classifier (the automatic reviewer used in auto mode) see the content or the reference.\n\n- The original reference is put back for the record of the tool call.\n\n- The call then reuses that content instead of reading the file again when sending.\n\n- The tool's MCP information is marked with `remoteFileReferenceFill: true`.\n\n- The size of the stored content is kept within limits.\n\n**Why**\n\nWhen you approve a file upload, you can see what is actually being sent, and what is sent is the same content you approved rather than a fresh read of the file.\n\n- Area: MCP\n- Names: `approvalSeesContent`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}