Unverified50% confidenceFactExact time
The MCP protocol itself does not specify a permission model; specific authorization is negotiated between client and server, and Smart Post Studio's "read/draft/schedule" tiers are its own self-designed permission granularity.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe MCP protocol specification defines message formats such as capability negotiation, tool invocation, resource reading, and prompt templates, but deliberately does not specify concrete implementations of authentication, authorization, and auditing.78% similarUnverifiedMCP tool calls trigger real operations (writing to databases, sending emails, etc.), so permission control and audit logging are especially important at the MCP server layer, which differs from API integrations that are primarily read-only queries.76% similarUnverifiedThe MCP protocol does not require clients to report clientInfo truthfully; the field is self-declared and there is no server-side verification mechanism.75% similarUnverifiedMCP annotations are only requests to the client rather than guarantees, and actual behavior still needs to be clearly stated in server instructions.73% similarUnverifiedIn the MCP design, agents cannot escalate their own permissions; privilege escalation must loop back to request user approval, keeping control in the hands of the user.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1071136API
curl https://kongchang.com/api/v1/knowledge/claims/1071136MCP
get_claim(id=1071136)