If I had to guess, I'd say that this behaviour is by design. SELECT queries are by definition safe for Monarch to run; that is, they cannot modify your source data in any way.
Note that Monarch doesn't make Data Definition or Update queries available either.
Having said that, I can't think of how a union query could be "dangerous", but my SQL's a bit rusty.
I'm sure other contributors will be along shortly to elaborate.