research use of aggregator field

does anybody see pitfalls, i.e. net.damage, if we used an aggregator to
mark some funny stuff in an announcement? i.e. there is a prefix being
announced that we would like to occasionally 'dye' with kinky values in
the aggregator attribute. can you see possible damage to others?

[ consultation with a few protocol folk came up with no damage cases.
  but we thought it would be nice to check with ops folk too ]