Three things are written next to every rating. None of them moves the level up or down.
- Restore path
- One of the three states above, for every loss. Where a confirmed restore would change the level, we say so: “High; Medium if the restore path is confirmed”.
- Attribution
- MCP-specific, platform-inherited or shared, from the vendor API control. It says whose code to fix. It does not lower the level: the data is as gone either way.
- Reachability
- When the failure needs an input the tool’s own schema or the platform’s API rejects as invalid, such as an out-of-range number or a wrong type, we say so. It does not lower the level.
A history that is documented but untested fails in ordinary ways: a retention cap, a beta API version, a write path that skips the log. And a restore is never free: the loss was silent, so someone has to notice it first, and a version restore discards whatever was saved afterwards.
- Confirmed by test
- In the audit, or in a dated follow-up test on its own fixtures, we restored the lost value from the platform’s own history, with what an ordinary user can reach. Rated Recoverable, with how and when.
- Documented, not tested
- The platform documents a history that should hold the value, but we did not restore from it. Rated as lost, with what would need verifying.
- None found
- No history or restore action that an ordinary user can reach.
Tested so far, in a follow-up on 14 November 2026 on the audits’ own test repository and local Grafana instances: git history gave back, byte for byte, the files GH-02, GH-03 and GH-15 deleted or overwrote, and dashboard version history gave back the values GF-01, GF-02 and GF-19 lost, on Grafana 11.6.16 and 13.3.0 (GF-19 on 13.3.0 only, the version that serves v2 dashboards). All six rate Medium. Grafana’s versions_to_keep setting defaults to 20.
From the vendor API control, run for every finding.
- MCP-specific
- The platform’s own API does not fail this way, or no API call compares. The fix belongs in the MCP server.
- Platform-inherited
- The platform’s own API fails the same way and the server passes it on. The fix belongs in the platform; the agent still meets the failure through the server.
- Shared
- Both contribute: the platform fails this way in some cases, and the server removes a protection or adds cases of its own.
HighC1 · PostHog MCP server
Two concurrent PATCHes to different fields of one insight drop one write; both callers get success.
- Rubric inputs
- Silent loss · Majority (7 of 11 pairs through the MCP server) · Vendor API: same failure (6 of 11 straight to PostHog’s API) · Impact: lost, no restore path confirmed · Scope: one field per pair
- Attribution
- Platform-inherited. PostHog merged the fix for insights.
- Why High
- High on impact, like GH-01: in both, one caller’s change is gone and both callers were told it worked. What differs is whose code to fix, and that is what the attribution says.
- Article label
- wrong write, medium
C1 in the audit