Control traffic with plugins
Plugins are where you configure how Fabric AI Gateway handles traffic. They can authenticate callers, protect sensitive data, transform requests and responses, observe LLM usage, and control traffic across LLM, MCP, and HTTP API routes.
Some behavior is provided by system plugins. For example, creating a connection with Gateway auth set to Gateway key adds Key Auth to the new route. Other plugins are configured as plugin instances that you attach to a scope.
Start with a capability
- Authenticate callers: Key Auth requires a gateway key on a route. Fabric adds it when you create a connection with Gateway auth set to Gateway key. See Authenticate requests with Key Auth.
- Protect sensitive data: PII Redaction detects and redacts configured personal data in LLM and MCP traffic.
- Transform requests and responses: Transformer can rewrite headers, query parameters, bodies, and cookies on supported routes, including LLM, MCP, and imported HTTP APIs.
- Observe LLM traffic: Use Analytics and traces to review usage, cost, latency, errors, and individual requests.
- Control cost: Set spending budgets and token-based limits, and use adaptive model routing. See Control spend with budgets.
Plugins run in an ordered policy chain, where they can inspect, allow, deny, or rewrite traffic at different points in the request lifecycle. The catalog below lists built-in plugins by category and the following sections show how to configure them.
Browse plugins by category
The catalog groups plugins into the following categories: Auth, Governance, Observability, Routing, Traffic, and Transform.
The Transformer and Validator plugins are the most versatile. Both can run in the request and response phases and can read nearly every available field. Transformer can change headers, query parameters, body, status, and cookies. Validator only adds a marker header. They can do so only when scoped globally, to a connection, or to a route.
Add a plugin instance
A plugin in the catalog doesn’t do anything on its own. To apply it to traffic, create a plugin instance that attaches the plugin to a scope and configures it.
To add a plugin instance, do the following:
- In the sidebar, select Plugins.
- On the All tab, find the plugin you want, such as Transformer or Rate Limit. Use Search plugins or the filters to narrow the list.
- Next to the plugin, click Use. The New plugin instance form opens.
- Enter a Name for the instance. Names must be unique. Reusing an existing name replaces that instance. You can’t change the name after you create the instance.
- Select a Scope kind, such as global or route. Some plugins can be scoped only to a route. If you choose a scope narrower than global, also select one or more Scope name values, such as specific routes. Fabric creates one instance for each.
- Under Configuration, configure the plugin using its dedicated form, or click Edit as JSON to provide raw configuration. Edit as JSON isn’t available for Rate Limit, Passthrough, or Adaptive Model Router.
- Optionally, expand Match conditions and status and add Match conditions to limit when the instance runs:
- Path prefix
- Methods
- Only run for consumer
- Only run for consumer group
- Under Status, confirm that Enabled is on. Fabric saves disabled instances but skips them at request time, so you can stage a configuration without activating it.
- Click Save.
To review the plugins that you’ve already set up, select the Configured tab.
Example: Rewrite a header with the Transformer plugin
The following example adds a transform that sets an X-Api-Key header on every matching request.
- Add a plugin instance and select Transformer as the plugin.
- Under Transforms, set the following values:
- Phase:
Request - Operation:
set - Target:
Header - Name:
X-Api-Key - Value:
prod
- Phase:
- Review the Compiled policy (Rego) panel. This panel is a read-only preview of the OPA policy that the control plane compiles from your transform and ships to the data plane’s sidecar.
- Click Save.
Example: Rate limit an MCP route
The following example limits traffic to a specific MCP route.
- Add a plugin instance and select Rate Limit as the plugin.
- Set Scope kind to route and Scope name to the route you want to limit, for example
linear-mcp. - Under Configuration, set Count by to one of the following:
- Consumer: One counter per authenticated caller. Requires authentication on the route.
- Credential: One counter per API key. Fabric fills this counter only when Key Auth is in use.
- Global: One counter for every request. This is the only option that works without authentication.
- Set Limit, the number of requests allowed per window. This field is required.
- Set Window (seconds). The default is
60. - Click Save.
To see how a plugin’s execution appears in request traces, see Inspect traces.
Guides for specific plugins
Next steps
- To review how your plugins affect traffic, see Monitor gateway traffic.
- To connect another provider, see Manage connections and routes.

