This feature provides the same functionality as sensitive routes on GraphQL endpoints.
Some routes may be more prone to bot attacks than others. For example, routes that execute payments or handle personal information. You can configure these routes as sensitive to ensure a more stringent protection. The Enforcer will make Risk API calls on such sensitive routes, even if the request contains a valid, unexpired cookie.
TO configure a sensitive GraphQL operation:
EXAMPLE
To learn more about custom subroutines, see Customized subroutines.
TO enable the feature: