It is great idea. Having a property to control whether a Service Action or Event can be used in ODC Workflow will add a valuable layer of control. It prevent misuse in teams with varying experience levels and promotes better governance and clean architecture.

 it may add a bit of overhead in managing access across actions especially in larger apps but the benefits in safety and maintainability definitely outweigh that.

This is a very valid point and a thoughtful suggestion. Giving developers control over which Service Actions and Events can be used in ODC Workflows would greatly enhance the governance and safety of workflow design—especially in environments where not all users are fully trained developers. 

While it may introduce some additional overhead in managing access permissions across actions—particularly in larger applications—the advantages in terms of safety, maintainability, and architectural control far outweigh the complexity. This level of granularity ensures that only intended logic is exposed to workflows, reducing the risk of misuse and promoting cleaner, more manageable application structures.