Anatomy of a hold
A hold is a decision with three exits, not an error.
Read Fig. 05 as text
|- HELD filesystem - write_file
ChangeKind added-required-param (1) fixed taxonomy. never free prose.
pinned write_file(path, content) (2) your baseline. what you saw first.
live write_file(path, content, (3) what the server sends now.
mode *)
* newly required
posture guard (4) why it held here. monitor would notify.
blast radius WRITE - not reversible (5) what the call would have done.
- stays on this machine
-> re-pin -> reject -> tune posture (6) three exits. all reversible.
the gate says "this changed", never "this is unsafe".A held call reads: HELD, filesystem write_file. ChangeKind added-required-param, a fixed taxonomy rather than free prose. Pinned: write_file with path and content, which is your baseline. Live: write_file with path, content and a newly required mode parameter, which is what the server sends now. Posture guard, which is why it held; monitor would only notify. Blast radius write, not reversible, stays on this machine. Three exits are offered: re-pin, reject, or tune the posture. All three are reversible.
Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.
Paste under the figure. That is the whole licence obligation.
<a href="https://mcpindex.ai/diagrams/anatomy-of-a-hold">Anatomy of a hold - mcpindex.ai</a> (CC BY 4.0)Standalone image/svg+xml. Vector, editable, no stylesheet needed.
https://mcpindex.ai/diagrams/anatomy-of-a-hold/svgLast reviewed 2026-07-27
mcpindex held my call · what does mcp hold mean · mcp gate hold output · mcpindex first hold