While Kupfer is right that Atril uses a JavaScript library, that doesn't actually mean that it executes JavaScript included in a PDF file.
You can see in this bug report for the Evince project (which Atril forked from) that JavaScript support has been discussed but has not been added.
As far as Atril JS support goes, the only thing I've found is a PDF rendering library also called "atril." It doesn't seem to be related. So you shouldn't have to worry about rogue JavaScript in your PDFs using either Atril or Evince.
Finally, I personally have been using Firefox as my PDF viewer. I've also recently disabled JavaScript execution; I read some PDFs from small personal websites and would rather not let my reading habits become a backdoor (though that may have already happened, actually).
I originally followed the instructions in this tutorial, but here they are in short form:
Enter about:config into the URL bar >>> Search for the pdfjs.enableScripting setting >> click the double-arrow symbol to the right of the setting to switch it to "false."