The openvas-nasl call looks valid / good.
It might be possible that the HTTP service was overloaded during the “full” scan of GVM causing a trigger of this message.
There is currently no reliable way to detect such situations, that’s also the reason why writing such active Denial of Service VTs was stopped many years ago.
The following post has some more info around this topic: