Currently, Jinja expressions in inputs are automatically rendered when the workflow loads. This creates a risk of unintended Jinja injection, especially when handling data from external sources or URL parameters.
To improve security and control, it would be helpful to have an option that prevents inputted Jinja from being evaluated immediately upon workflow execution.