Description: Users often would like to enforce some prompt guard or moderation policies to protect applications which uses the LLMs. The feature would fit for some enterprise users who build internal LLM/GenAI gateway by Envoy AI Gateway.
Describe the desired behavior, what scenario it enables and how it
would be used.
[optional Relevant Links:]
- Concept:
- Gateway Implementations
- Other Guard/Moderation Implementations
- Guard/Moderation API
Any extra documentation required to understand the issue.
From the API level perspective, I just imagined that the feature might be integrated into AIGatewayRoute or would introduce new API(CRD) to configure the guard/moderation policy because such policies are complex.
Perhaps, BackendTrafficPolicy or SecurityPolicy could be a candidate for integration target. But, these APIs are not Envoy AI Gateway's one. So, I think we should design more generic apis so that it can call external apis in this case.
Note: although Envoy AI Gateway does not support this feature natively, users could achieve this by implementing External Processing or External Authrization
Description: Users often would like to enforce some prompt guard or moderation policies to protect applications which uses the LLMs. The feature would fit for some enterprise users who build internal LLM/GenAI gateway by Envoy AI Gateway.
[optional Relevant Links:]
From the API level perspective, I just imagined that the feature might be integrated into
AIGatewayRouteor would introduce new API(CRD) to configure the guard/moderation policy because such policies are complex.Perhaps,
BackendTrafficPolicyorSecurityPolicycould be a candidate for integration target. But, these APIs are not Envoy AI Gateway's one. So, I think we should design more generic apis so that it can call external apis in this case.Note: although Envoy AI Gateway does not support this feature natively, users could achieve this by implementing External Processing or External Authrization