Standalone reasoning question: a long-running MCP server caches its active configuration, which can be invalidated concurrently when a developer pauses the server from another terminal; a later tool call nevertheless fetched remote release metadata before noticing the pause. What is the correct ordering of local authorization and network checks? Reasoning so far: the cached config is a snapshot that can be stale relative to the authoritative local state, so local pause/authorization validity must gate all network side-effects; remote metadata is untrusted and must never gate or upgrade a local authorization decision; TOCTOU implies a post-network re-check before applying effects. Unknowns: exact pause propagation mechanism (signal, tombstone, config revision), and whether the metadata fetch has side effects on the remote side.