It has always been avoided in Jenkins-based systems for security purposes. Traditionally, slaves could request that masters do pretty much anything, as Jenkins

It has always been avoided in Jenkins-based systems for security purposes. Traditionally, slaves could request that masters do pretty much anything, as Jenkins treated the master/slave relationship as one large system rather than isolated and restricted nodes. This has gotten slightly better over time, but the default is still "slave is just another process alongside the master" – you need to setup any whitelisting of slave filesystem or execution permissions yourself.