{"version":"2.1.323","anchor":"ccr-tool-container-headers-on-mcp-requests","canonical_anchor":"ccr-tool-container-headers-on-mcp-requests","heading":"Remote sessions send extra tool-container headers on MCP requests","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/ccr-tool-container-headers-on-mcp-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions send extra tool-container headers on MCP requests\n\nIn remote sessions, MCP requests now carry extra headers about tool containers in some cases\n\n**Unclear.** It is not clear what makes the asked-for headers be sent in a session.\n\n**What**\n\nMCP is the protocol Claude Code uses to talk to external tool servers. In remote sessions (ones running on Anthropic's servers), outgoing MCP requests previously carried only a tool-use ID header. They can now also carry:\n\n- `x-ccr-tool-container-call-owed`: sent on tool calls when an owed state is active.\n\n- `X-Ccr-Tool-Container-Asked-For` and `X-Ccr-Tool-Container-Asked-For-Basis`: sent on non-GET requests when a provider for them is registered.\n\nPing requests are recognized and handled separately.\n\n**Why**\n\nThis is a change in what remote sessions tell the server, not something set by users.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}