Hey @MattGudenas!
I’m not sure I follow your example. I agree that if not careful, a uploaded script might be able to access environment variables used in your app, though I don’t think that this would impact other tenants. Your app’s invocation(s) run in isolation from both the tenant and other installations of your app. App data (excluding any storage data your app might be using) is passed to the invocation of the app in the AWS Lambda. This data that is passed through, including environment variables and invocation information, is a copy of any data that you have configured. Changing it will only change it for that invocation of your app.
If I understand your example correctly, each invocation of your app isolates BOTH the runtime and any uploaded scripts together. There shouldn’t be any possibility of editing global variables for your app that is persisted beyond the single invocation for that script.
If I haven’t understood your example, did you have an example script/app that reproduces your concerns so that I may better understand?
Thanks!