MRY Tower Controller reported an aircraft on a SID turned the wrong direction on initial climb and flew below the Minimum Vectoring Altitude.

Narrative

Aircraft X departed RWY 10R. Upon departure the aircraft was visually seen to start a right turn. This is opposite of the given TORO 7 departure procedure and puts the aircraft in close proximity to high terrain. As Local Control (LC) I asked the pilot of Aircraft X to 'verify in a left turn for the TORO 7'. The aircraft responded 'standby' and was still seen visually turning right. I instructed the aircraft at that time to 'fly heading 060.' This is a vector below the MVA; but it is the TORO 7 departure procedure heading and it moved the aircraft out of the high terrain and to the lower terrain. The aircraft continued to climb and once at a safe altitude was switched to NCT [TRACON] with no further issues. The pilot was given a pilot deviation and after speaking with the pilot it appeared to have an FMS issue. Pilot stated they had the FMS programed for the TORO 7 departure but that the system used the 'NAV mode' instead of the 'heading mode' on departure; causing the right turn.This is not the first time that an aircraft has done something other than the assigned departure procedure. Because of our surrounding high terrain this can cause issues when we subsequently try to correct the aircraft and move them to a safe area. Clarification on what we can do bellow the MVA would help alleviate this confusion. Right now; it makes it seem like vectoring an aircraft to lower MVA area; as a controller; we still get 'in trouble'. Looking more into the .65 on vector below the MVA rules it is possible that we may need to include in a facility directive what to do with aircraft below the MVA.