Cloud Metadata Endpoint
A local HTTP service provided by cloud providers for cloud instances, used to query sensitive information such as instance identity and temporary credentials. It is accessible only from within the instance. The typical address is 169.254.169.254.
Timeline (last 90 days)
The Fetch MCP server by default rejects private, loopback, and link-local addresses (including the cloud metadata endpoint 169.254.169.254), and re-checks the target IP on every redirect hop.
Rule four: internal addresses stay closed—cloud metadata endpoints, loopback addresses, and private network addresses are not read no matter how the request is packaged.
Cloud metadata endpoints are local services that cloud providers offer to instances for querying sensitive information such as instance identity and temporary credentials, the typical example being AWS's 169.254.169.254.
The typical address of the cloud metadata endpoint is 169.254.169.254, and AWS, Azure, GCP, and others generally use similar addresses; it is reachable only from inside the instance and does not go over the public internet.
All Facts (4)
The Fetch MCP server by default rejects private, loopback, and link-local addresses (including the cloud metadata endpoint 169.254.169.254), and re-checks the target IP on every redirect hop.
50%UnverifiedRule four: internal addresses stay closed—cloud metadata endpoints, loopback addresses, and private network addresses are not read no matter how the request is packaged.
50%UnverifiedCloud metadata endpoints are local services that cloud providers offer to instances for querying sensitive information such as instance identity and temporary credentials, the typical example being AWS's 169.254.169.254.
50%UnverifiedThe typical address of the cloud metadata endpoint is 169.254.169.254, and AWS, Azure, GCP, and others generally use similar addresses; it is reachable only from inside the instance and does not go over the public internet.
50%