From 2d22491d6c97877ddba4a239380ea9c663b9a8d5 Mon Sep 17 00:00:00 2001 From: Maxim Bashurov Date: Tue, 4 Feb 2025 10:51:30 +0200 Subject: [PATCH] DOCS-2861 Little fixes to GraphQL rule --- docs/latest/api-protection/graphql-rule.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/latest/api-protection/graphql-rule.md b/docs/latest/api-protection/graphql-rule.md index 8ec202201..ad1146a67 100644 --- a/docs/latest/api-protection/graphql-rule.md +++ b/docs/latest/api-protection/graphql-rule.md @@ -17,6 +17,8 @@ Wallarm supports both POST and GET HTTP methods for GraphQL requests. ## Creating and applying the rule +GraphQL rule is recommended to be created for the GraphQL specific endpoints. Creating it as a [default](../user-guides/rules/rules.md#default-rules) rule for the entire system is not recommended. + To set and apply GraphQL policy: 1. Proceed to Wallarm Console → **Rules** → **Add rule**. @@ -42,6 +44,8 @@ To set and apply GraphQL policy: ![GraphQL thresholds](../images/user-guides/rules/graphql-rule.png) +Once created, the rule may be at any moment temporarily disabled and later re-enabled again using the **Mode** parameter of the rule. + ## Reaction to policy violation Reaction to the policy violation is defined by the [filtration mode](../admin-en/configure-wallarm-mode.md) applied to the endpoints targeted by the rule.