Unverified50% confidenceDecision RuleExact time
Agent scenarios must guard against SSRF attacks, forbidding crawling of private IP ranges (10.x, 172.16.x, 192.168.x, 127.x) and the cloud metadata endpoint 169.254.169.254, and re-validating the actual IP after DNS resolution to prevent domain-rebinding bypasses.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe runtime proxy firewall's SSRF protection includes blocking internal URLs (such as localhost, 169.254.169.254, 10.x, 192.168.x), validating redirect chains (at most 3 hops, no protocol downgrade), preventing DNS rebinding, and extracting and validating embedded URLs through deep document inspection.78% similarUnverifiedCommon practices for defending against SSRF include: resolving the target domain name to an IP and then determining whether it falls within restricted ranges such as private address ranges, link-local addresses, and loopback addresses; restricting protocols to only allow http/https; and re-performing validation after each redirect.77% similarUnverified防御SSRF需对用户可控的URL做协议白名单、禁止访问内网地址、过滤file://等危险协议72% similarUnverifiedBlocklisting private addresses and metadata addresses by default is the most fundamental and critical step in defending against SSRF attacks, and developers implementing MCP tools with network access capabilities should refer to this approach as a priority.66% similarUnverifiedMalware typically does not hard-code IP addresses, but instead locates C2 servers through domain name resolution to enable rapid switching after an IP is blocked; the related techniques are known as Fast Flux or Domain Generation Algorithms (DGA).66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062903API
curl https://kongchang.com/api/v1/knowledge/claims/1062903MCP
get_claim(id=1062903)