{"version":"2.1.284","anchor":"remote-routed-tools-deny-on-a-failed-permission-check","canonical_anchor":"remote-routed-tools-deny-on-a-failed-permission-check","heading":"Tools running on another machine are refused if their permission check fails","tier":"notice","area":"Remote Hosts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/remote-routed-tools-deny-on-a-failed-permission-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Tools running on another machine are refused if their permission check fails\n\nA tool routed to another host is now refused outright when its permission check cannot be completed\n\n**Unclear.** Exactly which tools count as routed to another host.\n\n**What**\n\nSome tools run on another machine instead of your own. When the permission check for one of these tools cannot be completed, Claude Code now refuses the call and reports that it was not run because its permission check could not be completed. Before, the decision was handed to the local version of the tool, and only when that tool defined how to handle a failed check.\n\n**Why**\n\nAn action on another machine does not go ahead when Claude Code cannot confirm it is allowed.\n\n- Area: Remote Hosts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}