{"version":"2.1.246","anchor":"remote-permission-checks-use-deterministic-synthetic-tool-id","canonical_anchor":"remote-permission-checks-use-deterministic-synthetic-tool-id","heading":"Remote permission checks use deterministic synthetic tool ids","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/remote-permission-checks-use-deterministic-synthetic-tool-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Remote permission checks use deterministic synthetic tool ids\n\nRemote permission checks build placeholder tool ids deterministically from the session and original id.\n\n**What**\n\nWhen a relayed request asks for tool permission on behalf of remote execution, the placeholder tool-use id it constructs is now a prefixed sha256 of the session id and the original id, truncated to 32 hex characters, instead of an arbitrary value. Only the remote-execution relay path is affected.\n\n**Evidence**\n\n`sha256`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}