One alternative would be simply to not access from the slave. Use the "Archive the artifacts" option to push them from the volatile workspace on the slave to the builds (logs) directory on the master. Then you effectively retrieve them from the master.
Posts here (my similar response), here, here and here provide some insight on usage. Also, official documentation from Jenkins
pipeline here.
You can then use Copy Artifacts Plugin to retrieve them from the other job and use them or retrieve directly using your groovy script.
ps: You will probably want to carefully manage the # builds you keep and as suggested in the prior response, consider using the system property jenkins.model.Jenkins.buildsDir
to store all the build logs (and artifacts) outside of the jobs config directory.
This response provides an alternative solution using groovy and reading node's workspace, but you are then dependent on the node being up, the workspace not being wiped and a job not to be in progress.