{"version":"2.1.323","anchor":"mcp-file-and-artifact-permission-cards-reworked","canonical_anchor":"mcp-file-and-artifact-permission-cards-reworked","heading":"Connector tool calls that pass a file object are refused with a clear message","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-file-and-artifact-permission-cards-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Connector tool calls that pass a file object are refused with a clear message\n\nClaude Code no longer sends a file through a tool argument holding an object with an id, a mimeType and a size, and says the tool was not called\n\n**What**\n\nWhen a tool from a connector (an MCP server, an outside program that gives Claude Code extra tools) has an argument holding an object with an id, a mimeType and a size, Claude Code does not send a file through it. Instead it returns an error saying no file was sent and the tool was not called.\n\nThe permission prompts for MCP files and for the Artifacts tool were also reworked. There is a new outcome for a request that was denied before. Artifact creation notices are now handled for subagents, which are helper agents that Claude starts to work on part of a task.\n\n**Why**\n\nA connector call that tries to pass a file this way now stops with a message saying why, instead of going through.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}