{"version":"2.1.246","anchor":"interrupting-an-mcp-tool-call-now-says-the-call-may-have-run","canonical_anchor":"interrupting-an-mcp-tool-call-now-says-the-call-may-have-run","heading":"Interrupting an MCP tool call now says the call may have run anyway","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/interrupting-an-mcp-tool-call-now-says-the-call-may-have-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Interrupting an MCP tool call now says the call may have run anyway\n\nInterrupting an MCP call now warns you it may have run on the server anyway.\n\n**What**\n\nAn MCP call aborted mid-flight used to come back as an empty error. It now returns a result marked as interrupted with text warning that the call may or may not have completed on the server and should be verified before you assume it did not.\n\n**Details**\n\n- The aborted path previously returned no content and only an error flag; it now returns content plus both `interrupted` and `isError`.\n- Both MCP client paths check the interrupted flag after a call and raise that dedicated message rather than a generic failure.\n- Downstream rendering uses the flag to separate a user interruption from a tool failure.\n\n**Evidence**\n\n`The tool call was interrupted before a result was received. It may or may not have completed on the server`, `interrupted: !0, isError: !0`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}