The irony of LLMs flagging standard interactive UI code as potentially harmful

Was benchmarking a local open-source model last night, trying to generate a basic script for a high-velocity, randomized matrix animation (essentially a dynamic grid that handles quick-cycling numeric variables and auto-refresh intervals). Nothing crazy, just raw Javascript and math variables.

To my complete lack of surprise, the system threw a massive corporate safety tantrum. It flagged the request as "potentially high-risk automated behavior" and hit me with the standard, preachy 3-paragraph lecture about digital safety guidelines.

It’s getting completely ridiculous. We’ve reached a point where standard dynamic front-end logic triggers the exact same censorship algorithms as actual malicious scripts. The corporate fear of anything that calculates numbers faster than a human typing has completely broken the utility of these assistants.

Out of sheer frustration, I shut down the local environment and spent the rest of my evening exploring a fast, heavily optimized independent web platform just to analyze how their engineers managed to build a completely unfiltered, heavy-volume dynamic grid without lagging the browser infrastructure or relying on centralized safety nodes. The contrast is staggering — seeing real-time, high-density data loops run instantly in the wild while our coding tools are locked inside a padded room.

Are you guys experiencing similar absurd blocks when prompting for complex visual setups, or are you strictly using unmoderated local weights now to bypass this nonsense?