Diagrams · Fig. 06

It held. Now what?

Every exit from a hold is reversible.

It held. Now what?A decision tree for a held call. If you expected the change, re-pin and the new contract becomes your baseline. If you did not expect it, ask whether it is breaking or destructive: if yes, reject the call, check the server changelog, and check the public ledger to see whether the crawler saw it too; if no, re-pin or move that server to the monitor posture. If the gate is holding too often, move from guard to monitor to notify and proceed, or to strict, which holds anything it cannot prove benign.HELDdid you expect this change?YESre-pin. the new contract becomes your baseline. done.NOis the change breaking or destructive?YESreject the call. check the server’s changelog, and check /ledger tosee whether the crawler caught the same drift.NOre-pin, or move that one server to the monitor posture.holding too often?guard → monitornotify and proceed. you still see every change.guard → stricthold on any drift, including benign.EVERY EXIT IS REVERSIBLE. A RE-PIN CAN BE RE-PINNED.
Fig. 06 · Every exit from a hold is reversible.
Read Fig. 06 as text
  |- HELD
     |
     +- did you expect this change?
     |     yes --> re-pin. the new contract becomes your baseline. done.
     |      no --> is it breaking or destructive?
     |                 yes --> reject the call. check the server's changelog.
     |                         check /ledger - did the crawler see it too?
     |                  no --> re-pin, or move that server to the monitor posture.
     |
     +- holding too often?
           guard --> monitor    notify and proceed. you still see every change.
           guard --> strict     hold anything not PROVEN benign.

  every exit is reversible. a re-pin can be re-pinned.
What the figure says

A decision tree for a held call. If you expected the change, re-pin and the new contract becomes your baseline. If you did not expect it, ask whether it is breaking or destructive: if yes, reject the call, check the server changelog, and check the public ledger to see whether the crawler saw it too; if no, re-pin or move that server to the monitor posture. If the gate is holding too often, move from guard to monitor to notify and proceed, or to strict, which holds anything it cannot prove benign.

Where this is explained
/guides/install-the-gate-first-hold/guides/tune-postures
Use this diagram

Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.

Credit line (HTML)

Paste under the figure. That is the whole licence obligation.

<a href="https://mcpindex.ai/diagrams/it-held-now-what">It held. Now what? - mcpindex.ai</a> (CC BY 4.0)
Direct SVG

Standalone image/svg+xml. Vector, editable, no stylesheet needed.

https://mcpindex.ai/diagrams/it-held-now-what/svg

Last reviewed 2026-07-27

Questions this answers

mcpindex re-pin &middot; mcp gate too many holds &middot; mcpindex posture &middot; what to do when mcp call is held