Only if they require compilation. There may still be an open policy about installing scripting language modules especially in personal work areas, on the assumption that scripting languages allow less direct access to the OS and so less possibilities to subvert security and load balancing policies. A classic example is an account on a shared web server that provides ssh access to a shell. ftp and wget may be enabled but not make,cc, or other tools viewed as CPU intensive. Sometimes it isn't even security - it is just a way of crippling the account so that they can steer heavier users into higher priced VPS accounts.
Is this wise? Does it really make things secure? Don't these servers have automatic shut-offs that kill processes if they consume too many resources? We can debate. But it is what is.