{"version":"2.1.314","anchor":"mcp-tool-host-permission-declined-requests-now-acknowledged","canonical_anchor":"mcp-tool-host-permission-declined-requests-now-acknowledged","heading":"Tool calls served over MCP handle repeats and declined permissions","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-tool-host-permission-declined-requests-now-acknowledged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Tool calls served over MCP handle repeats and declined permissions\n\nTool calls from another host are no longer run twice, matching permission requests are joined, and declined requests are acknowledged\n\n**What**\n\nClaude Code can offer its own tools to another program over MCP (a protocol for connecting tools). When such a call comes from another host:\n\n- A call that was already started is not run again. It returns \"was not run again: this very call was already started here once\".\n\n- A permission request that matches one still waiting for an answer is joined to it rather than asked a second time.\n\n- A permission request that was declined is now acknowledged and answered with a result, instead of falling through to the general case. The path for a request that was not honoured now also reports which part was affected.\n\n**Why**\n\nA host that retries a call no longer causes the tool to run twice or a second permission prompt to appear, and a declined permission is reported back to the host.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}