{"version":"2.1.323","anchor":"mcp-tool-calls-artifact-audience-retry-and-relative-path-re","canonical_anchor":"mcp-tool-calls-artifact-audience-retry-and-relative-path-re","heading":"MCP calls that create shared items can be retried after your approval","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-tool-calls-artifact-audience-retry-and-relative-path-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP calls that create shared items can be retried after your approval\n\nSome MCP calls that fail over who an item is shared with are retried after an approval prompt, and relative paths are refused without a folder\n\n**Unclear.** It is not clear which sessions or MCP servers the approval retry applies to.\n\n**What**\n\nMCP servers are programs that give Claude extra tools. Two things are different when Claude calls them:\n\n- A call that fails because it did not say who a new item should be shared with, and that carries a sharing value, is retried with that value set. The retry always shows you an approval prompt first, and if Claude Code cannot run its safety check the call is refused.\n\n- A session with no working folder now refuses calls that use a relative path (a path that only makes sense from a starting folder), with a message saying it cannot check the call against its permission rules.\n\n**Why**\n\nYou may now be asked to approve MCP calls that create something shared, and calls Claude Code cannot check are refused 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"}