Can you run it? Read its code? Redistribute it verbatim? Make modifications to the code for private use? Redistribute the modifications? Then it's free software.
You are free not to like some free software licenses though.
Your answer proves that GP has a point: Commons Clause (on top of Apache for instance) fits your requirements perfectly, yet it is not "free software" according to FSF/OSI definitions.
There are degrees to freedom, and while FOSS activists would like to paint issues black and white, they really are not. Which freedoms a particular user cares about is not at all given. For myself, I would gladly use Commons Clause software, because if I make money off software then it's only fair that I pay commercial license for it - after all, it's in my interest that the software is actively developed and maintained. And your questions are really all I care about, and this clause conforms to them.
But I think in the end it is up to each user to decide which set of freedoms they care about to the point of not using non-conforming software. The cynic in me would say that most users care only about free (as in beer) - at least judging by Android and plethora of its free-of-cost apps.
EDIT: I am not arguing that Commons Clause & co. should be accepted under the "free license" term - for better or worse, this term has some widely accepted definition that is not compatible with them. Maybe a new term, like "hybrid licenses" is needed? We'll see.
I doubt that "can you run it?" is meant to be interpreted as: "can you run it, sometimes?"
To GP:
> There are degrees to freedom, and while FOSS activists would like to paint issues black and white, they really are not
There are software that are free software, and software that are not free software. This is the whole point of a good definition. Actually assessing whether a program is free software might be hard, but at the end no software is between free software and non-free software.
Now we can argue on a level of freedom but we are not talking about this definition anymore.
You can't run Commons Clause software if you're receiving payment for doing so. You can't redistribute Commons Clause software verbatim if you're receiving payment for doing so. (As written, it even appears to prohibit selling a CD of the software for the cost of the blank CD, a service that's otherwise widely accepted as a useful community contribution.)
Because the Commons Clause restricts the situations in which you can run and redistribute the software, software licensed under it isn't free software.
Is it free software? No. Does it allow many more freedoms than closed source? Hell yes. Is that enough? We'll see.
MIT or BSD -> "Open"
MIT or BSD: free, open source
GPL: free, open source, copyleft