Hi Francesco,
You misunderstand what mmcau_aes_set_key can do. When you look at the mmCAU library code in KSDK, you will find the comment for this function as follows.
# AES: Performs an AES key expansion
# arguments
# *key pointer to input key (128, 192, 256 bits in length)
# key_size key_size in bits (128, 192, 256)
# *key_sch pointer to key schedule output (44, 52, 60 longwords)
#
# calling convention
# void mmcau_aes_set_key (const unsigned char *key,
# const int key_size,
# unsigned char *key_sch)
So what it does is part of the AES algorithm for key expansion, and the generated key schedule are used in the rounds for AES algorithm. What you want to store is just the input key, 128bit for AES-128.
And to your question on how you can prevent reading back the 128bit security key, I suppose you mean prevent reading back from JTAG instead of user code running in flash. If that's the case, then you can just secure the flash and put internal flash into NVM special mode. Under this mode, lots of flash commands are not allowed. Also you can stored the security key into the flash IFR area with program once command, the key can only be read back with read once command with user code.

For details on how to enable flash security, you can check the following application note.
http://www.nxp.com/files/microcontrollers/doc/app_note/AN4507.pdf?fasp=1&WT_TYPE=Application%20Notes...
Hao