There is only one action, really - running a program that is marked (by its programmer) as needing admin-level access.
Which is what the MS article really says:
User Account Control (UAC) notifies you before changes are made to your computer that require administrator-level permission.
Perhaps some technical explanation might help:
The OS has always(*) implemented permissions on objects and privileges on accounts. Some objects have permissions only grant access to admins; some operations inherently require privilege. Prior to UAC:
1) If an admin attempted a system call involving some sort of protected/privileged access, it would be allowed.
2) If a non-admin attempted the same thing, the call would fail, and the program could handle the error or not, as it chose.
Was there ever a list of programs that contained system calls needing elevated access? I doubt it.
With UAC, the admin sort of looks a lot like a non-admin. But in addition, UAC permits a program to declare, before it is run, that it needs elevated access. This is where prompting and/or quiet elevation can occur, depending on whether you're signed on as an admin or not.
(Programs that do not carry the requisite declaration will just get
executed in the unprivileged context and likely fail as per (2) above)
Doesn't help you with getting a list; I'm just explaining why I don't think you'll find such a list. I could be wrong, though.
(*) I speak only of the Windows NT line of descent, not the DOS/Windows family.