If you're looking for actual guidelines for those, I'm not sure if there are any well-established ones.
Tool-wise, I recently stumbled across Nitriq. At the time of writing, it's free (as in beer), and is extremely easily extensible via LINQ-style queries on top of their analysis model. You could probably create a query for the metrics you mention, within a few minutes.
Edit: I would also advise against using metrics in any other way than to explore the codebase and guide code-reviews. Being forced to comply with ill-conceived, automated, artificial metrics can be quite irritating. Not every situation is the same, and not everyone agrees with specific metrics. I also tend to stick to the simpler metrics - e.g. SourceMonitor offers line of code and cyclomatic complexity measures (min, max, average, by project, class, method, etc). At a glance, this gives me 95% of what I want to know, without getting too technical. You'll notice the "red flags" immediately.