Restricting the maximum number of tokens in an operation helps prevent excessively large operations reaching your landscape. This can be useful to prevent DDoS attacks, Heap Overflows or Server overload.
You can configure graphql-protect
to limit the maximum number of tokens allowed on an operation.
max_tokens:
# Enable the feature
enable: true
# The maximum number of allowed tokens within a single request.
max: 1000
# Reject the request when the rule fails. Disable this to allow the request regardless of token count.
reject_on_failure: true
This rule produces metrics to help you gain insights into the behavior of the rule.
graphql_protect_max_tokens_results{result}
result |
Description |
---|---|
allowed |
The rule condition succeeded |
rejected |
The rule condition failed and the request was rejected |
failed |
The rule condition failed but the request was not rejected. This happens when reject_on_failure is false |
No metrics are produced when the rule is disabled.