Though I'm using HTTPS the attacker might get the access token by intercepting the request with burp suite
This means that the attacker has a certificate trusted by the client. HTTPS does not protect against MITM by a trusted party, which in case of Burp suite is often the client themselves (i.e. reverse engineering the app).
Such MITM could do anything in the name of the user anyway, by modifying any requests passing through or injecting script into the responses. There is no need to explicitly know the access token for this, i.e. protecting the access token would not help here anyway.
That said, the access token is basically an authentication method which relies on sending the secret to the server, similar to a password. There are authentication methods which only prove the knowledge of a shared secret without sending the secret itself, like Digest authentication. There are also methods which rely on asymmetric cryptography to prove knowledge of the private key, like client certificates or signing some server provided challenge. In these cases the secret itself is never transmitted. But it will still not protect against attacks by the client itself using Burp suite or similar, because the client might extract the necessary secrets from the client app.