Is there some address list or rules for forbid users to connect via teamviewer?
i found some, but somehow it goes throguh.

script for drop trafic for address-list
/ip firewall filter
add action=drop chain=forward comment="Drop all traffic from address on TeamviewerServers" src-address-list=TeamviewerServers
add action=drop chain=forward comment="Drop all traffic from address on TeamviewerServers" dst-address-list=TeamviewerServers
add action=drop chain=input comment="Drop all traffic from address on TeamviewerServers" src-address-list=TeamviewerServers

Are you sure those address lists are correct ?

Is this a comedy thread LOL.
First of all that is not a script just a few lines of firewall filter.
Second, what are the contents of teamviewer servers? All you have identified is the name of the List LOL.

Since TV uses ports 80 and 443 it may be a bridge too far.
The only quote I found thus far : I managed to block teamviewer by adding regexp in L7protocol, but for all IP address.
Not sure if that still applies or how CPU intensive it may be???

The most pertinent question is. WHY DO YOU WANT TO BLOCK IT??
The best answer is. If it is against company policy then you don't want to block it - you want to log it, present it to HR and discipline the culprit.
(or against Home policy......... same same).

Not sure if that still applies or how CPU intensive it may be???

Not terribly, as these L7 rules would likely be used on DNS queries (which requires to redirect any DNS request from the client to your own DNS, which the client can beat using some counter-measure like secure DNS so you end where you began) and DNS queries are not there all the time and the relatively simple regexp matches on the very first (and only) packet.

If it is against company policy then you don't want to block it - you want to log it, present it to HR and discipline the culprit.

Well, the key is to identify that traffic; what you use that identification for is less important. Sure, to log it, it is best not to restrict it, because then you can just log outgoing connections to TCP and/or UDP port 5938 and 99.9% of them are teamviewer ones. Once you block the port 5938, the application will revert to 443 or 80, which you can only block for particular IP addresses if you can't block web access completely.

One option would be blocking by DNS (assuming MikroTik is used as DNS server). This is not a very good way and can be relatively easy bypassed (but any VPN/Tor will bypass anything and there are many other remote access/screensharing tools).
P.S.
If you are using Active Directory I suggest looking at Software Restriction Policies.
If you are using Active Directory, most likely domain controller (not MikroTik) is used as DNS server.
If you are trying to block IT people, they will find a way how to bypass almost any technical restrictions (administrative measures will be more effective then).

P.P.S. I like @sindy's idea (identifying connections to port 5938 and taking administrative measures).

P.P.P.S. Instead of the unreachable route a filewall entry like this could be used to privide logging as well: