Unverified50% confidenceDecision RuleExact time
The MCP server must treat parameters coming from the Agent as untrusted external input, and must not assume they are safe just because the request comes from its own Agent.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen an MCP server cannot reliably identify the client making a request, any entity that can reach that service endpoint may obtain data or invoke tools under the guise of a legitimate client.78% similarUnverifiedThe MCP specification requires that tool annotations be treated as untrusted unless the server is trusted.76% similarUnverifiedIn the MCP architecture, the Agent only forwards invocation requests to the server, and the server executes I/O and side effects, so permissions, auditing, and sandboxing can all be handled uniformly on the server side.76% similarVerifiedAt the authorization layer, an MCP server can act as an intermediary proxy responsible for holding, managing, and rotating access credentials, so that the Agent itself does not need to directly handle the underlying keys75% similarUnverifiedBecause MCP Servers are independently deployed external services, their versions and behavior may change without the Agent's awareness.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1029728API
curl https://kongchang.com/api/v1/knowledge/claims/1029728MCP
get_claim(id=1029728)