Additional protection from possible stackoverflow

We are going to use Jint in the production at the back-end of highly customizable cloud web application. The source of the scripts will be our users so we can not trust to the scripts. Moreover if user accidentally writes script which causes stackoverflow it will shut down the whole application. As soon as we can not afford it we will use in production version of Jint with two additional options preventing uncontrolled recursion as a main source of accidental stack overflows. 
See unit tests to get an idea how is going to be used.
I think I got the reason by looking at the exceptions. You are just looking for recursions and not call stack depth. That works for me. But why have two exceptions then? I saw one is just a specific case of recursion 1 which means "no recursion allowed" as in 0. A single exception is sufficient.