{"version":"2.1.305","anchor":"drive-file-references-upload-files-without-typing-base64","canonical_anchor":"drive-file-references-upload-files-without-typing-base64","heading":"Google Drive connector can upload local files by reference instead of typed base64","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/drive-file-references-upload-files-without-typing-base64","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Google Drive connector can upload local files by reference instead of typed base64\n\nBehind tengu_wobbly_dewdrop, Drive's create_file can take a file reference that Claude Code reads after approval; HIPAA orgs are denied\n\n**What**\n\nThe Google Drive connector's `create_file` tool used to need the file's content typed out as base64 (file data written as text). A new path lets Claude pass a reference of the form `sha256:<hex>:<path>`. After you approve the call, Claude Code reads the file and fills in `base64Content` itself.\n\n- The tool's instructions gain a \"FILE REFERENCES\" section telling Claude to use a reference.\n\n- Files are limited to 10 MB.\n\n- It is controlled by the server-controlled switch `tengu_wobbly_dewdrop` and the policy `allow_drive_file_references`.\n\n- It is refused for third-party providers, custom base URLs, HIPAA and diskless sessions.\n\n- The new policy key is labelled \"File references for connectors\" (HIPAA-R87) and is denied under `hipaa`, including when the policy answer is missing or fails.\n\n- MCP tools marked as accepting file references are handled separately when tools are cached.\n\n**Why**\n\nLarge Drive uploads would no longer pass through Claude's output. HIPAA-scoped organizations have the feature denied by default.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: yes"}