{"version":"2.1.285","anchor":"mcp-ccr-approval-refuses-resend-on-some-sessions","canonical_anchor":"mcp-ccr-approval-refuses-resend-on-some-sessions","heading":"Approving an MCP request after the fact can now fail with an error","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/mcp-ccr-approval-refuses-resend-on-some-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Approving an MCP request after the fact can now fail with an error\n\nAfter you approve an MCP tool request after the fact, a new check can stop it from being sent again and raise an error\n\n**Unclear.** It is not clear when this check refuses to send the request again.\n\n**What**\n\nMCP is the way Claude Code connects to outside tools. When you approve such a request after it has already been held back, Claude Code used to carry on straight away. It now runs another check first, and that check can stop the request from being sent again. When that happens, the error code is `ccr_proxy_needs_approval_resend_refused`.\n\n**Why**\n\nThis is a rare error. If you see this code, the tool request was not sent again even though you approved it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}