Unverified50% confidenceDecision RuleExact time
MCP's design principle is that Discovery, Permission, Policy, and Runtime Assets must be separated from one another.
1
Sources
50%
Confidence
Long-term
Relevance
10/8/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMCP的设计哲学是上下文共享与统一访问方式，允许智能体与工具之间共享丰富的上下文信息77% similarVerifiedIn MCP's security design, tool invocations are stipulated to require explicit user authorization, and resource access is constrained by permission boundaries.75% similarUnverifiedMCP在Capability Discovery阶段需要声明所需操作权限，其权限声明机制借鉴了OAuth 2.0的Scope概念74% similarUnverifiedThe value of MCP is mainly reflected in cross-cutting scenarios involving multiple models and multiple tools; for products with a single model and a small number of fixed tools, its design goals exceed actual needs.74% similarUnverifiedIn the MCP architecture, the LLM is responsible for deciding which tool to call and MCP is responsible for execution, forming a division of labor where 'the model handles decisions and MCP handles execution'.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/987528API
curl https://kongchang.com/api/v1/knowledge/claims/987528MCP
get_claim(id=987528)