{"version":"2.1.315","anchor":"staged-mcp-call-inputs-can-be-written-through-a-safe-path","canonical_anchor":"staged-mcp-call-inputs-can-be-written-through-a-safe-path","heading":"Input files for mcp_call can now be written through a safer path","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/staged-mcp-call-inputs-can-be-written-through-a-safe-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Input files for mcp_call can now be written through a safer path\n\nFiles staged as input for mcp_call can now be written under a resolved real folder, guarding against redirected links\n\n**Unclear.** What decides whether the safer write is used is not stated.\n\n**What**\n\nBefore an `mcp_call` request runs a tool, Claude Code stages its input as files on disk. When a check passes, it now writes these files under the folder's real, fully resolved location instead of writing them directly. A failure is reported as \"input stage failed\".\n\n**Why**\n\nThis guards against a symlink (a file that points to another place on disk) being changed to point somewhere else, so staged input cannot be redirected to an unexpected location.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}