You can achieve above requirement by checking pyMaxRecords field on report definition rule.

The logic would be:

• Browse all report definition with filter criteria pyMaxRecords <=500

The clipboard structure for report definition page:

PageXX->pyContent->pyMaxRecords (refer attached screenshot)

You can refer below details to fetch all report definition in your application.

In the Data-Rule-Summary class you can create a report definition that returns a count for every rule type in the system.

This class contains the following properties that are essential for rule reports:
 pzInsKey — key of the rule instance. This property is useful for joining other classes as we might
do with Rule History reports.
 pyClass — the class of the rule type. For example, Rule-Obj-Property is for property rules.
 pyClassName — the Apply To class of the rule. This could be, for example, the work class of a
purchase request application.
 pyRuleSet and pyRuleSetVersion — the ruleset and ruleset version.
 pyRuleName — a unique identifier used by the system; for example, CountOfLineItems.
 pyLabel — a short description of the rule. For example, the label for the property named
CountOfLineItems — could be Number of Items to Purchase.
 pyRuleAvailable — the availability of a rule.
 pxUpdateDateTime, pxUpdateOperator, and pxUpdateOpName — the most recent update
information.

You can join other classes with the rule classes in order to provide more granular information. Some of the classes that are most commonly joined with the rule classes are:
 History-Rule instances represent rule updates.
 Data-Rule-Locking instances represent locks, or checkouts, of each rule.
 Index-Warning for rule warnings, like the performance warning that’s given if a non-optimized
property is used in a report.
 Index-CustomFields for custom fields defined for rules – a feature specifically designed to aid rule
reporting

Hope this will help.