Unverified50% confidenceDecision RuleExact time
Every MCP server and tool starts in a disabled state and must be explicitly reviewed and enabled by the responsible team.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/8/2026
First Seen
Valid until: 1/6/2027
Sources
Related Entities
Related Claims
UnverifiedThe MCP specification requires hosts to ask for user confirmation before running any tool, mandating that a human-in-the-loop step be retained.77% similarUnverifiedWhen configuring a custom MCP Server in the experimental field, it is necessary to disable the platform's built-in tools such as Amap Maps, Time, and Fetch to prevent conflicts.76% similarUnverifiedEach MCP Server is a read-only slice of the design system, filtered for a specific team, so different teams see different content.75% similarUnverifiedIn the MCP ecosystem, 'official' generally means the Server is maintained by the engineering team of the integrated service's original vendor, rather than being a third-party imitation.74% similarUnverifiedThe MCP specification requires that tool annotations be treated as untrusted unless the server is trusted.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/989220API
curl https://kongchang.com/api/v1/knowledge/claims/989220MCP
get_claim(id=989220)