Verified70% confidenceDecision RuleExact time
The MCP specification requires hosts to ask for user confirmation before running any tool, mandating that a human-in-the-loop step be retained.
4
Sources
70%
Confidence
Long-term
Relevance
7/17/2026
First Seen
Sources
Related Claims
UnverifiedA mature MCP gateway needs a built-in user consent flow capable of triggering confirmation before an Agent performs high-risk actions, recording user authorization status, and updating permissions when authorization changes78% similarUnverifiedWhen evaluating an MCP integration, one must confirm that permission checks occur on the server side in the context of each retrieval request, rather than relying solely on identity verification at connection initialization.78% similarUnverifiedEvery MCP server and tool starts in a disabled state and must be explicitly reviewed and enabled by the responsible team.77% similarVerifiedMCP's permission model is relatively coarse-grained: once a tool is registered, the agent can invoke it, lacking a context-aware risk assessment mechanism for individual calls, built-in operation rate limiting, or mandatory human approval processes.76% similarUnverifiedOmni MCP performs permission checks at the gateway layer, where the gateway verifies whether the caller has permission when a tool is actually invoked.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/547573API
curl https://kongchang.com/api/v1/knowledge/claims/547573MCP
get_claim(id=547573)