Nothing that can't already be spammed with macros, which come with the game. I could write a server script that would break this in two minutes, but that would also remove some functionality from the game altogether, and then I would feel obliged to write a work-around for BuildBot, which would be considerably more complex.
In the end, BuildBot would still work, but then it would be laggier and some other things on the server would be broken and everyone would be unhappy.
"Nothing that can't already be spammed with macros", Can't and won't are two different things. Buildbot makes it rediculously easy to load massive scale builds, any gibblet could load something big and annoying. Whereas if you want to load a macro, you have to first save it. And saving massive builds brick by brick by recording a macro is so tedious that nobody in their right mind would attempt it. Keeping it from being annoying.
I think a solution would be to make the entire mod server-sided, and have it require permission from the host or an active admin before a load can be used. For example: Someone tries to use it, a request is sent to a super admin, that can be denied or approved. That would keep the mod as being useful, and solve the abuse problem.