nice idea, but I'm unsure how to deal with the security issues this would bring along...
after all the script would expose internal information to users not allowed to.
...or do I see it wrong?

Agreed, the security aspect would be tricky. I am not familiar with how Scriptler currently handles security, does it have different levels? Perhaps you make another level for this so o ly certain script can be used? The idea of using a Scriptler script in an email was submitted to me for email-ext, but I thought if Scriptler could expose a token that would be useful in many places.

yeah, maybe we can mark some scripts to be public an these would then be fine to be used in a macro

Code changed in jenkins
User: imod
Path:
.gitignore
pom.xml
src/main/java/org/jenkinsci/plugins/scriptler/ScriptlerManagment.java
src/main/java/org/jenkinsci/plugins/scriptler/tokenmacro/ScriptlerTokenMacro.java
src/main/java/org/jenkinsci/plugins/scriptler/util/GroovyScript.java
src/main/resources/org/jenkinsci/plugins/scriptler/Messages.properties
src/test/java/org/jenkinsci/plugins/scriptler/ScriptlerManagementHelper.java
src/test/java/org/jenkinsci/plugins/scriptler/tokenmacro/ScriptlerTokenMacroTest.java
http://jenkins-ci.org/commit/scriptler-plugin/1f5a83c5ab43c04a00113f087bb0d22db0b87193
Log:
[FIXED JENKINS-17708] Expose scriptler scripts via token macro token