NeuralTrust | Platform for Agent Security.

The request_size_limiter policy rejects requests whose body exceeds a configured limit, before they’re forwarded upstream — a cheap guard against accidental or abusive oversized prompts. It runs at pre_request.

Configure in the console

Policies → Catalog → Request size.
Set max payload size (and unit), max characters, and whether Content-Length is required.
Choose scope (gateway-wide or targeted) and save.

Setting	Type	Default	Notes
`allowed_payload_size`	int	`10`	Max body size, in `size_unit`.
`size_unit`	enum	`megabytes`	`bytes` · `kilobytes` · `megabytes`.
`max_chars_per_request`	int	`100000`	Max characters in the request content.
`require_content_length`	bool	`false`	Reject requests with no `Content-Length`.

{
  "slug": "request_size_limiter",
  "settings": {
    "allowed_payload_size": 5,
    "size_unit": "megabytes",
    "max_chars_per_request": 50000
  }
}

Run it as a global policy at pre_request to set a gateway-wide ceiling, or scope it to specific consumers for tighter per-tenant limits.

Introduction

Getting started

Resources

Endpoints

Routing

Policies

MCP

Observability

API reference

Request size

Configure in the console

​Configure in the console

Configure in the console