{"version":"2.1.281","anchor":"hooktoolcall-payload-strips-isreadonly","canonical_anchor":"hooktoolcall-payload-strips-isreadonly","heading":"Hook\/tool.call payload strips isReadOnly","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/hooktoolcall-payload-strips-isreadonly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Hook\/tool.call payload strips isReadOnly\n\ntool.call events now have their isReadOnly field removed before they are passed on\n\n**Unclear.** The finding does not say which consumers receive this reduced payload, including whether user-configured hooks do.\n\n**What**\n\nEvery time Claude uses a tool, Claude Code produces a `tool.call` event describing that tool call. Before this event is handed on, the step that prepares it now deletes one field, `isReadOnly`, which says whether the call only reads things.\n\n**Why**\n\nAnything that received `tool.call` events and looked at `isReadOnly` will no longer find it there."}