Unverified50% confidenceCautionExact time
The 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.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/8/2026
First Seen
Valid until: 1/6/2027
Sources
Related Entities
Related Claims
UnverifiedWithout rigorous authentication, permission isolation, and input validation, a hijacked agent may cause damage to backend systems via an MCP server.76% similarUnverifiedMCP 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.74% 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 integrations73% similarVerifiedImproperly configured MCP Servers can lead to security risks such as database password leakage, exposure of private files, and token theft.72% similarUnverifiedUsing DCR in MCP scenarios has drawbacks including Client ID proliferation, lack of validation, secret management burden, and scenario mismatch.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/988572API
curl https://kongchang.com/api/v1/knowledge/claims/988572MCP
get_claim(id=988572)