Configuration to control Maximum Transactions per Robot

Is there a possibility to limit the maximum number of transactions per Robot or per Queue. The requirement is from Security perspective, for e.g.
-we want to control how many requests a robot can trigger to our applications during a given time frame.

Additional question:
-If robot is not using orchestrator queue but is connected to orchestrator, we still want to control if any malicious actions , bulk junk data entry into our applications etc that may occur

I understand that these have to covered in Security centric code reviews depending upon the workflows being automated, but looking for suggestions if any such control measures can be also implemented using Orchestrator jobs (designed specifically for robot monitoring) or Queue configurations etc. as a baseline.