Limits on built-in classes are being ignored

During sanity testing it came to light that limits specified on built-in classes stopped working, likely as a result of merging #2568 (closed). Given the following snippet:

"client-classes": [
    {
        "name": "ALL",
#        "name": "water",
#        "test": "not member('KNOWN')",
        "user-context": {
            "limits": {
                "address-limit": 2
            }
        }
    }],

The limit works fine if the class is named "water" and "test" is included. When named, "ALL", a built-in class with "test" commented out (tests are not allowed for built-in classes), the limit is ignored.

See #2613 (comment 324969).