{"version":"2.1.302","anchor":"upload-task-file-tools-apply-launch-permission-rules-via-rul","canonical_anchor":"upload-task-file-tools-apply-launch-permission-rules-via-rul","heading":"Remote file upload tools now apply the session's permission rules","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/upload-task-file-tools-apply-launch-permission-rules-via-rul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Remote file upload tools now apply the session's permission rules\n\nUpload and remote file tools now apply the permission rules the session was launched with, through one shared step\n\n**What**\n\nWhen Claude Code runs as an MCP server, a mode where another program uses it as a tool provider, it offers tools for remote file work such as UploadTaskFile and ReadProjectUploadText. These tools now work out their inputs and permission rules through one shared step. Before, they passed the inputs and the launch permission settings along directly. A related warning about a settings file now names ListDirectoryForRemote alongside ReadFileForRemote.\n\n**Why**\n\nPermission handling for remote file operations is tighter.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}