Block & throttle abusive requests

Editor assessment

The subject states a real protective capability, abusive requests are blocked and throttled, which is important information, but chore is a doubtful type for what is plainly a security feature where feat belongs, and the misfit misleads anyone scanning for protection work. No scope, no body explaining the thresholds or the mechanism, rack-attack rules presumably, and only a Co-authored-by trailer otherwise. Hygiene is fine: imperative shape, no trailing period. Understandable and valid, miscast and unexplained, hence acceptable. The thresholds an operator needs are nowhere stated.