Can the F5 Advanced WAF protect the JWT token in an HTTP authorization header?

Hello,

 

Can the F5 Advanced WAF protect the JWT token in an HTTP authorization header?

 

My idea is that the F5 can monitor a cookie or parameter from tampering but what about if the a JWT token is used and the client changes the HTTP header with another value that is not a web attack but another stolen JWT token.