Unverified50% confidenceTradeoffExact time
Annotation declarations on MCP servers have no enforcement validation mechanism at the protocol level, creating a supply-chain trust problem where an attacker can publish a malicious server claiming to be read-only while performing arbitrary write operations.
1
Sources
50%
Confidence
Long-term
Relevance
10/8/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMCP tool annotations (such as read-only, destructive, idempotent, and open-world) are hints rather than guarantees, and applications should treat them as untrusted information unless the server itself is trusted.80% similarUnverifiedThe official Learn documentation notes that autonomously running or misconfigured clients may execute destructive operations, and that flags for blocking destructive operations have not yet been standardized in the MCP protocol.75% similarUnverifiedCritics point out that an MCP Server with file system write permissions, once exploited by malicious tools, would present an attack surface harder to audit than traditional API integrations72% similarUnverifiedHow to ensure that sensitive call content of MCP servers is not leaked when connecting to third-party analytics tools is a data privacy issue that remains to be verified.72% similarVerifiedImproperly configured MCP Servers can lead to security risks such as database password leakage, exposure of private files, and token theft.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/988971API
curl https://kongchang.com/api/v1/knowledge/claims/988971MCP
get_claim(id=988971)