If you need all the variables then not quite;
let {block_active, allow_rtc_onoff, allow_scheduler, allow_solar, block_mode, message_limit, counter, messages_yesterday, messages_today, block_mode_previous} = global.get( 'MQTT', "file").MQTT
The MQTT file is not the MQTT Object, just a container for the Object
[{"id":"a63d08342b71197c","type":"inject","z":"7fdabd9.f693544","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"{\"MQTT\":{\"block_active\":true,\"allow_rtc_onoff\":\"on\",\"allow_scheduler\":true,\"allow_solar\":true,\"block_mode\":true,\"message_limit\":null,\"counter\":2,\"messages_yesterday\":20,\"messages_today\":2,\"block_mode_previous\":\"\"}}","payloadType":"json","x":2470,"y":420,"wires":[["dd6be678775335e5"]]},{"id":"dd6be678775335e5","type":"function","z":"7fdabd9.f693544","name":"function 12","func":"context.set(\"loadsOfThings\", msg.payload)\n\nlet {message_limit, allow_rtc_onoff} = context.get(\"loadsOfThings\").MQTT\nmsg.message_limit = message_limit\nmsg.allow_rtc_onoff = allow_rtc_onoff\n\nreturn msg","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":2670,"y":420,"wires":[["5ce9fa176e991281"]]},{"id":"5ce9fa176e991281","type":"debug","z":"7fdabd9.f693544","name":"debug 244","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":2890,"y":420,"wires":[]}]
a quick demo to show what I mean. But other than that, yes, but only if you need them all and if so why not just
let MQTT = global.get('MQTT', 'file')
The advantage of global.get( 'MQTT', "file").MQTT
is that it could be global.get( 'loadsOfStuff', "file").MQTT
and 'loadsOfStuff'
can be many other Objects - global.get( 'loadsOfStuff', "file").somethingImportant