The point that hashing tool definitions detects metadata drift but not behavior changes behind an unchanged schema is an important caveat, and often missed. A useful complement is pinning the server package or image by digest and diffing its network egress against a baseline, since a rug pull can happen entirely in code. Do you think approval UIs should also surface a tool's declared annotations (like readOnlyHint) as untrusted hints rather than as guarantees?