Unverified50% confidenceFactExact time
MCP only specifies "how to expose tools," not "when which tool should be called"—this is precisely the root cause, repeatedly emphasized in the article, of why the implicit operational rules cannot be solved by the protocol.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/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.80% similarUnverifiedMCP的设计中Server是被动的，不思考、不决策，只暴露工具等着被调用76% similarVerifiedMCP 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.76% similarUnverifiedMCP 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.74% similarUnverifiedThe tool has a built-in function for pinning MCP tool definitions, and issues a warning when a connected MCP server subsequently modifies its tool definitions.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1023301API
curl https://kongchang.com/api/v1/knowledge/claims/1023301MCP
get_claim(id=1023301)