Hi Team,
Product Idea: Execution‑Rate Limits and User Verification Workflow for Plugin Actions
Problem
Plugins can be triggered repeatedly within a short time window—either due to automation loops, misconfiguration, or unintended user behavior.
When a Plugin executes more than an expected number of times in a defined period, it introduces risks such as:
- Unintended system changes being applied repeatedly
- Increased load on downstream systems
- Potential security concerns if repeated execution indicates misuse or compromised credentials
- Loss of user trust if actions occur without clear intent
There is currently no native mechanism in Moveworks to rate‑limit Plugin executions or to validate authenticity when abnormal execution patterns occur.
Proposed Capability
Introduce a configurable execution‑limit framework for Plugins, allowing administrators to define:
- Max execution count (e.g., 10 executions)
- Time window (e.g., within 1 hour, 24 hours, etc.)
- Trigger conditions (per user, per device, per workflow, or global)
When the threshold is exceeded, Moveworks should automatically:
- Pause further executions of the Plugin.
- Notify the end user (or admin) that the Plugin has been triggered unusually often.
- Request confirmation from the user to validate authenticity.
- Resume or block execution based on the response.
Regards,
Sravani S