Skip to main content
Feedback

JSON Threat Protection Policy Configuration Values

Updated 23 June 2026

The following configuration values can be defined while configuring the JSON Threat Protection policy on the Call Transformation page:

note
  • Only pre-processing is applicable for this policy. Post-processing is not applicable.
  • Setting a limit to -1 disables that check, allowing selective structural protection.
Field nameTypeField ValueRequired/OptionalDescription
Processing AdapterStringcom.mashery.proxy.protection.json-threat-protectionRequiredAdapter that validates JSON request bodies against configured structural limits and rejects threats with HTTP 400.
Perform Pre-processingBooleanEnabled / DisabledRequiredWhen enabled, the policy inspects the JSON request body before forwarding the request to the backend.
Data to make available for pre-processing (PreInput Values)Map
Integer (-1 to specify no limit)maxEntriesOptionalThe maximum number of entries allowed for a JSON object. For example, in { "a": { "b": 1, "c": 2, "d": 3 } }, the object a has three entries. Default: 100.
Integer (-1 to specify no limit)maxArraySizeOptionalMaximum number of elements allowed in a JSON array. Default: 100.
Integer (-1 to specify no limit)maxDepthOptionalMaximum nesting depth of the JSON structure. For example, { "a": { "b": { "c": true } } } has a depth of three. Default: 100.
Integer (-1 to specify no limit)maxNameLengthOptionalMaximum string length allowed for a JSON property name. Default: 100.
Integer (-1 to specify no limit)maxValueLengthOptionalMaximum string length allowed for a JSON property value. Default: 500.

Configuration Steps

Refer to Configuring Call Transformation in Legacy UI for more information on the configuration steps.

On this Page