Apparently there is the breakpoint keyword (documentation), though I think it is on a per line basis, so the debugger will just stop once it reaches that line without any way to control when it stops.
While not a great solution, you may be able to pause the game to see what is happening. You can quit/close the application by calling get_tree().quit(), but for debugging that might not be helpful. Neither solution is ideal though, they are more workarounds than proper solutions. I'll keep an eye out for a better solution and if I find one I'll post it here.