Autosaver gotchas?

What would be a good way of safely running a Python Autosaver script at fixed intervals in MotionBuilder?

You know, I’m thinking I wouldn’t want to try and save a file while motion builder is already opening/saving, running a script or otherwise busy.

Is there a way of checking for an “idle” state or system event type, before running the auto save? Or will MB simply defer such a script until it’s not busy?