NeuralTrust | Platform for Agent Security.

For LLM function-calling traffic, TrustGate can shape which tools the model sees and how often they run. Create policies under Policies → Catalog, or attach them from a consumer Policies tab.

Policy in the catalog	Slug	Catalog group	What it does
Tool Injection	`tool_injection`	Tool Governance	Append operator-authored function tools to the request before the model runs.
Per-Tool Rate Limiter	`per_tool_rate_limiter`	Traffic Control	Limit how often a tool name/pattern may execute (LLM and MCP).

These policies apply to the LLM request tools[] / tool-call path (and, for the rate limiter, to MCP tool executions). They are not the same as MCP toolkit grants on a consumer or role, which control which MCP server tools an agent may list and call — see MCP.

Tool Injection

tool_injection injects operator-authored function tools into the outbound request so the model can call them. It does not filter or deny client-supplied tools — it only adds gateway tools (and resolves name collisions).

Configure in the console

Policies → Catalog → Tool Injection (Tool Governance group).
Under Inject tools, add one or more functions:
- Name (required)
- Description (optional — helps the model choose when to call it)
- Parameters (optional JSON Schema object for arguments)
Set On conflict when an injected name collides with a client tool.
Set mode and scope (gateway-wide or targeted consumers), then save.

Settings

Setting	Meaning
Inject tools	At least one function tool. Each entry is a `function` with `name`, optional `description`, optional `parameters` schema.
On conflict	When an injected name already exists on the request: Gateway tool wins (`gateway_wins`, default), Client tool wins (`client_wins`), or Reject the request (`reject`).

Stage: pre_request. Protocol: LLM only.

{
  "slug": "tool_injection",
  "settings": {
    "inject_tools": [
      {
        "type": "function",
        "function": {
          "name": "get_internal_status",
          "description": "Return internal service health",
          "parameters": {
            "type": "object",
            "properties": { "service": { "type": "string" } }
          }
        }
      }
    ],
    "on_conflict": "gateway_wins"
  }
}

Per-Tool Rate Limiter

per_tool_rate_limiter counts real tool executions (not generic HTTP requests) and enforces one or more time windows per tool pattern. It works for LLM tool calls and native MCP tool traffic. In the catalog it lives under Traffic Control (not Tool Governance), next to the request rate limiter.

Configure in the console

Policies → Catalog → Per-Tool Rate Limiter.
Add rules. The first rule whose tool pattern matches a tool call wins.
For each rule set:
- Tool — glob against the tool name (e.g. execute_code*, search_*)
- Windows — one or more { duration, max } pairs (e.g. 1m / 60, 1h / 500)
- Optional per-rule behavior (otherwise the policy default applies)
Set the default behavior when a window is exceeded.
Save.

On exceed (behavior)

Behavior	Effect
Reject response (`reject_response`)	Fail the call (default). On MCP, this is the only behavior that can be attached — the gateway is the tool caller, so the request cannot be rewritten.
Inject error result (`inject_error_result`)	Rewrite the response with an error tool result (LLM, response path).
Strip tool from request (`strip_tool_from_request`)	Remove the tool from the next request (LLM, request path).

Counters follow policy scope: gateway-wide for global policies, otherwise per consumer.

{
  "slug": "per_tool_rate_limiter",
  "settings": {
    "behavior_default": "reject_response",
    "rules": [
      {
        "tool": "execute_code*",
        "windows": [{ "duration": "1m", "max": 10 }]
      }
    ]
  }
}

What is not a catalog policy

Control	Where it lives
MCP toolkit (which MCP tools/prompts/resources an agent may use)	Consumer Routing / MCP binding, or Roles `mcp_policies` — see MCP.
Which LLM models a consumer may call	Filter by available models / default model on the consumer (or role) Routing tab — see Model resolution.

Policies overview
Rate limiting & budgets — request-volume and token/dollar budgets
MCP — toolkit scoping for MCP servers
Playground — exercise LLM tool-using consumers

Introduction

Getting started

Console

Core concepts

Routing

Policies

MCP

Observability

Operate

Admin API

API reference

Tool governance

Tool Injection

Configure in the console

Settings

Per-Tool Rate Limiter

Configure in the console

On exceed (behavior)

What is not a catalog policy

​Tool Injection

​Configure in the console

​Settings

​Per-Tool Rate Limiter

​Configure in the console

​On exceed (behavior)

​What is not a catalog policy

​Related

Tool Injection

Configure in the console

Settings

Per-Tool Rate Limiter

Configure in the console

On exceed (behavior)

What is not a catalog policy

Related