AbuseFilter uses Title::getRestrictions for all *_restrictions_* variables, and it seems like the method doesn't handle cascading restrictions.

I'd like to see this information in AF variables, no opinion as to the best way to accomplish it (including if a different variable should be used). A related item may be for edits that are protected by other means as well (such as a namespace protection, or a page type protection).

@Xaosflux for sure this would be useful. As for how, we'll probably just have to add another call to a core method and merge the result. Or maybe getAllRestrictions + filtering would be enough. However, IMHO we cannot do it now: old AbuseLog entries (before rEABF42bd0d84f4244ca2304c6d161f71d90a6a53030c in 2013) are associated with a full AbuseFilterVariableHolder object serialized in the DB. Unfortunately, this object contains non-computed variables as well, which are computed on the fly whenever you examine that hit. If we change the method used to compute restrictions vars, then their content will also be changed for such entries.
The solution is T213006, which aims to remove non-computed variables, but until then we'd be forced to add extra code for back-compat, and I'd rather avoid it.