I dont think thats possible now, we only have below options.
root@SRX# set security alarms potential-violation ?
Possible completions:
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
authentication Raise alarm for specified number of authentication failures (1..10)
cryptographic-self-test Raise alarm for cryptographic self test failures
> decryption-failures No. of decryption failures before which an alarm needs to be raised
> encryption-failures No. of encryption failures before which an alarm needs to be raised
idp Raise alarm for idp attack
> ike-phase1-failures No. of IKE Phase-1 failures before which an alarm needs to be raised
> ike-phase2-failures No. of IKE Phase-2 failures before which an alarm needs to be raised
key-generation-self-test Raise alarm for key generation self test failures
non-cryptographic-self-test Raise alarm for non-cryptographic self test failures
> policy Raise alarm for flow policy violations
> replay-attacks No. of Replay attacks before which an alarm needs to be raised
security-log-percent-full Raise alarm when security log exceeds this percent capacity (0..100)