Unverified50% confidenceFactExact time
MCP only addresses the standardization of connectivity and invocation, and is not responsible for security; responsibilities such as authentication and authorization, approval of dangerous operations, and verification of service trustworthiness must be handled by the application layer.
1
Sources
50%
Confidence
Long-term
Relevance
9/3/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMCP协议本身并不携带工具的风险语义，安全判断的责任落回应用开发者手中77% similarUnverifiedIn MCP's security design, tool invocations are stipulated to require explicit user authorization, and resource access is constrained by permission boundaries.76% similarUnverifiedMCP currently remains focused on standardizing tool discovery and invocation formats, while fine-grained permission management control has not yet been incorporated into the core protocol constraints.74% similarUnverifiedMCP currently lacks fine-grained permission control, and third-party servers of unknown origin may contain malicious instructions.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/850778API
curl https://kongchang.com/api/v1/knowledge/claims/850778MCP
get_claim(id=850778)