{"version":"2.1.242","anchor":"tool-calls-with-a-late-host-argument-are-rejected-instead-of","canonical_anchor":"tool-calls-with-a-late-host-argument-are-rejected-instead-of","heading":"Tool calls with a late host argument are rejected instead of run","tier":"notice","area":"Tool Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/tool-calls-with-a-late-host-argument-are-rejected-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Tool calls with a late host argument are rejected instead of run\n\nLocal tool calls that get a host argument too late now fail instead of running.\n\n**What**\n\nBoth the streaming and the direct tool-execution paths now check, before running a locally-executed tool, whether it was handed a host argument that arrived too late, and fail the call with a dedicated error rather than executing it.\n\n**Evidence**\n\n`late host argument on a local tool call`\n\n- Area: Tool Execution\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}