Is it OK to forward the current access token or request new token for Proxy

TL;DR

I need to create a Proxy between the client app and the webapi, e.g.

client app <---> proxy <---> webapi (secured by oauth2)

Should the proxy just forward the access token to the webapi, or request a new access token?

Detailed

Currently, there're a client app and a webapi. To access the webapi, the client app needs to proivde the access token.

i.e. client <---> webapi (secured by oauth2)

Everything works as expected.

However, for some reason, there's a new requirement which is to create a proxy server using asp.net core in between the client and the webapi.

i.e. client <---> proxy <---> webapi

The proxy code is just like below:

[Route("api/[controller]")]
[ApiController]
public class ProxyController : ControllerBase
{
    [Authorize]
    [HttpGet]
    public async Task<ActionResult<object>> Invoke()
    {
        using (HttpClient client = new HttpClient())
        {
            //GET ACCESS TOKEN FROM CURRENT REQUEST
            var accessToken = await HttpContext.GetTokenAsync("access_token"); ;
            client.SetBearerToken(accessToken);
            var response = await client.GetAsync("https://demo.identityserver.io/api/test");
            if (!response.IsSuccessStatusCode)
            {
                return response.StatusCode;
            }
            else
            {
                var content = await response.Content.ReadAsStringAsync();
                return content;
            }
        }
    }
}

As you can see, I just use the current access token and then make the request to the real api.

For security's sake, I've no idea is it Ok to make use of the current access token. Should I request a new access token for the proxy and make request to the real api?