What it does
- Inspects agent requests to determine which tools are being requested (PreRequest)
- Applies an allow/deny policy using a whitelist and/or denylist
- Edits the request to remove disallowed tools; continues with allowed ones
- Permissive behavior on parsing issues (request is allowed if no tools are detected or content can’t be parsed)
Configuration Parameters
| Parameter | Type | Description | Required | Default |
|---|---|---|---|---|
white_list | array | List of tool names explicitly allowed | Cond. | [] |
deny_list | array | List of tool names explicitly denied | Cond. | [] |
provider | string | LLM request format provider (e.g., openai) | No | openai |
white_list or deny_list must be provided.
Behavior notes:
- Stage: PreRequest
- If there is no body, no tools, or parsing fails, the request proceeds unchanged
Prerequisites
These agent security plugins require upstreams configured in provider mode. See Upstream Services & Routing for details: /trustgate/core-concepts/upstream-services-overview Example upstream (provider mode):Example configuration
Whitelist example (only allow specific tools):Compatibility
Currently supports agents using the OpenAI LLM request/response format only.Best practices
- Prefer
white_listin sensitive environments to reduce risk surface - Keep lists concise and review them regularly as your agent evolves
- Combine with Tool Guard (content risk) and Tool Budget Limiter (cost control)