{"version":"2.1.304","anchor":"image-read-can-be-aborted-mcp-at-resource-read-gated-by-skil","canonical_anchor":"image-read-can-be-aborted-mcp-at-resource-read-gated-by-skil","heading":"MCP resources inside a skill's folder are only read if the skill lists them","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/image-read-can-be-aborted-mcp-at-resource-read-gated-by-skil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### MCP resources inside a skill's folder are only read if the skill lists them\n\nClaude Code now refuses an @-mentioned MCP resource in a loaded skill's folder unless the skill lists it, and image reads can be cancelled\n\n**What**\n\nYou can @-mention a resource from an MCP server (an outside service connected through the Model Context Protocol) to bring it into the conversation. If that resource sits in the folder of a loaded skill, a skill being a reusable set of instructions, Claude Code now refuses to read it unless the skill lists it. The message says the resource was not read because it is in the folder of a loaded skill.\n\nSeparately, reading an image from a pipe or device can now be cancelled partway through.\n\n**Why**\n\nA skill's files can no longer be pulled in through an @-mention unless the skill makes them available, which tightens what an MCP resource can expose.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}