Does 3ds Max offer a native sandbox for executing untrusted MAXScripts?

3ds Max versions from 2020 through 2025 execute MAXScript and Python code with the full privileges of the logged-in Windows user. This environment allows scripts to perform file system operations, launch shell processes via dosCommand, and interface with the .NET framework without any internal restriction layer.

While the documentation explicitly recommends running only trusted code, the application lacks a built-in sandbox, 'restricted mode,' or capability tokens to limit what a .ms or .mcr file can do. Furthermore, scene files can contain scripted controllers or callbacks that execute automatically upon loading, posing a risk when artists open assets from public forums or shared drives.

Is there any undocumented configuration within 3ds Max to restrict MAXScript's access to the filesystem or network? How can the application prevent the execution of malicious callbacks embedded in scene files without external OS security policies?