{"version":"2.1.277","anchor":"tengu-remote-tool-forward-telemetry-gets-a-caller-gate-field","canonical_anchor":"new-in-session-permission-check-before-forwarding-a-tool-cal","heading":"Remote tool calls now get an in-session permission check before forwarding","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/tengu-remote-tool-forward-telemetry-gets-a-caller-gate-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Remote tool calls now get an in-session permission check before forwarding\n\nTool calls forwarded to a bound or remote machine are now checked against in-session permissions first, and the check's result is logged as caller_gate\n\n**What**\n\nBefore a subagent's tool call is forwarded to a remote or bound machine, Claude Code now runs an in-session permission check (the same kind used for `canUseTool` decisions locally). If that check denies the call, it is refused immediately with a new outcome, `rejected_in_session`, and never reaches the remote host at all.\n\nThe `tengu_remote_tool_forward` telemetry event now records a new `caller_gate` field reflecting whether this in-session check ran and what it allowed, alongside the existing outcome and refusal fields.\n\n**Why**\n\nThis closes a gap where a tool call could be forwarded to a remote machine without first being checked against the permissions that would apply locally, and gives visibility into how often that in-session gate blocks a forward.\n\n- Area: Telemetry\n- Names: `tengu_remote_tool_forward`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}