It looks like this fix is a matter of exposing the same timeout param as defined in the top-level HTTP Request node that’s mentioned here:
timeout
HTTP Request
Into the same requestOptions object within the HTTP Request Tool definition, as listed here:
requestOptions
HTTP Request Tool