Verified65% 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.
3
Sources
65%
Confidence
Long-term
Relevance
9/3/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedThe MCP protocol itself does not carry risk semantics for tools, and the responsibility for security judgment falls back on the application developers.77% similarVerifiedIn MCP's security design, tool invocations are stipulated to require explicit user authorization, and resource access is constrained by permission boundaries.76% similarUnverifiedMCP is permission-based, and software companies only expose the features they are willing to open up, meaning commercially sensitive or core monetization features will almost never be included.75% similarUnverifiedEnterprises cannot let every Agent connect directly to various external services; an MCP gateway layer is needed to uniformly manage authentication, rate limiting, auditing, and policy enforcement.75% similarUnverifiedWhen enterprises evaluate MCP-based solutions, in addition to focusing on protocol compatibility, they also need to carefully review vendors' specific capabilities in security governance.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/850778API
curl https://kongchang.com/api/v1/knowledge/claims/850778MCP
get_claim(id=850778)