Filters
A filter is what turns AI governance on. It binds guardrails to a population, and for the Netzilo AI Gateway it also says what that population may use. Without a filter that matches, a device records and enforces nothing, and a gateway user is refused every model.
A filter has one of two types:
| Type | Targets | Carries | Enforced by |
|---|---|---|---|
| Endpoint | Devices in the filter's groups that run one of its operating systems. With the OS Browser, the Netzilo browser extension of the groups' users. | Agents (the apps to intercept) and Guardrails | The Netzilo client on each device; the browser extension for Browser |
| Gateway | Users in the filter's groups, when they go through the AI Gateway | Models, Limits, MCP servers and bundles, Gateways (the addresses users reach), Routing rules and Guardrails | The AI Gateway, per user |
Devices never load gateway filters, and gateways never load endpoint filters.
You manage filters under Edge > Governance > Filters. Only administrators and owners see this page.
How it works
Endpoint filters. A device gets a filter when it is in any of the filter's groups and its operating system is in the filter's list. When several filters match, their guardrails are merged into one rule set and evaluated together, most severe rule first. A block from any rule wins.
Browser. With the OS Browser, the filter reaches the Netzilo browser extension of every user in the filter's groups, matched by the signed-in user's groups, not by a device. A desktop OS value never reaches the extension, and a filter that lists only Browser never reaches a desktop client. List both when both should apply. See Browser Extension.
Gateway filters. A user gets a filter when any of the filter's groups is one of the user's groups. When several filters match, grants add up (models, MCP servers and bundles, gateway addresses), the lowest value of each limit applies, guardrails are merged, and the routing rules of all of them are evaluated together by priority.
The group All matches every device and every user.
Changes reach devices and gateways within seconds of saving. A gateway re-checks each user's filters about every 60 seconds.
Before you start
- Groups. Filters target groups. Put devices in groups with setup keys or under Endpoint > Peers, and users through your identity provider or Groups.
- Guardrails you want to bind, under Guardrails. You can also create one from inside the filter dialog.
- For a gateway filter: at least one provider with models, any limits, MCP servers or bundles and routing rules you want to apply, and the address of your AI Gateway.
The Filters list

| Column | What it shows |
|---|---|
| Name | The filter's name and description. |
| Active | Whether the filter is enabled. |
| Type | Endpoint or Gateway. |
| Groups | The groups the filter targets. |
| Models | For a gateway filter, the number of models granted, or a Grant Models badge when none is. A dash for endpoint filters. |
| MCP | For a gateway filter, the number of MCP servers and bundles granted, or Grant MCP. A dash for endpoint filters. |
| Guardrails | The number of guardrails the filter binds. |
Narrow the list with All, Active and Inactive, with the group selector, or with Search filters, groups, guardrails.... Click a row, or Edit, to open a filter.
Create an endpoint filter
Click Add Filter. The dialog Create New Filter opens on the Targets tab. For an endpoint filter the tabs are Targets, Agents, Guardrails and Name. Continue walks through them in that order.
Targets

| Field | What to enter |
|---|---|
| Filter Type | Endpoint: devices in the selected groups. Operating systems and agents apply. |
| Groups | One or more groups the filter applies to. Required. |
| Operating Systems | One or more of Windows, Mac, Linux, Android, iOS and Browser. Required. Browser targets the browser extension of the groups' users and nothing else. |
| Enable Filter | Turn the filter on or off without deleting it. On by default. |
A filter that targets only the browser extension lists just Browser:

Agents
Agents lists the apps whose traffic the Netzilo client steers into its inspecting proxy on Windows and macOS. Enter the path of each app's executable.

- Click Add Agent for each path, for example
%ProgramFiles%\Google\Chrome\Application\chrome.exe,/Applications/Cursor.app/**or~/.local/bin/claude. - Wildcards
*and**, and environment variables such as%PROGRAMFILES%and$HOME, are supported and expanded on the device. - Leave the tab empty for no transparent interception. Agent hooks, the SDK and the browser extension do not use this list.
- Linux has no per-app steering. On Linux use agent hooks, the SDK or the proxy settings, see Coding Agents and Custom Agents.
- A browser executable in Agents makes the desktop client inspect that browser, and the browser extension in it then stands down.
Then continue to the Guardrails and Name tabs, described below for both filter types.
Create a gateway filter
Click Add Filter and choose Filter Type Gateway. The tabs become Targets, Models, Limits, MCP, Gateways, Routing, Guardrails and Name.
Continue walks Targets, Models, Limits, Routing, Guardrails and Name. It skips the MCP and Gateways tabs: open them by clicking them. A filter saved without a gateway address grants its models, but users see no gateway in their Workplace and have nothing to paste.
Targets

| Field | What to enter |
|---|---|
| Filter Type | Gateway: AI gateways, for users in the selected groups. Endpoints skip this filter. |
| Groups | One or more groups whose users the filter applies to. Required. |
| Enable Filter | On by default. |
A gateway filter has no operating systems and no agents.
Models
Models grants the models users of this filter may call. At least one is required: the dialog does not save a gateway filter without one, and Continue stays disabled until you add one.

Click Browse Models. The dialog Grant Models lists every enabled model of your enabled providers. Tick single models, or All models of a provider, which grants every model the provider has, now and later. Click Apply (n).

A model is granted from one provider. If you have two providers of the same type, a grant of the first does not cover the second.
Limits
Limits applies spend budgets and rate limits to each user of the filter. Optional.

Click Browse Limits to pick limits from Edge > Governance > Limits, or Add Limit to create one here. Each limit counts per user, and when several filters apply to a user the lowest value of each kind wins. See Limits.
MCP
MCP grants the MCP servers and bundles users of this filter may call. Optional.

- Browse MCP Servers adds servers. Each grants All Tools, or, with the switch off, only the tool names you type, comma separated.
- Browse MCP Bundles adds bundles. A bundle grants the tools its definition lists.
Tool names are not checked: a misspelled name grants nothing. See MCP.
Gateways
Gateways lists where users of this filter reach their gateways. The Workplace shows each address with the models and MCP endpoints granted, so users can copy them into their tools.

Click Add Gateway and enter the gateway's address, an http:// or https:// URL without a
path, for example https://aigw.apps.example.com. The menu next to an address opens
Gateway Settings, where you set the name users see in the Workplace; without a name the URL is
shown. You can add several addresses and reorder them. How to publish the gateway at an address
is described on AI Gateway.
Routing
Routing lists the routing rules the filter applies to its users' requests: rules that send matching requests to other providers and models, by weight, with fallbacks. Optional. Without routing rules, requests go to the model they ask for.

- Browse Routing Rules picks rules from Edge > Governance > Routing Rules.
- Add Routing Rule creates a rule and adds it to this filter.
- The remove button on a row takes the rule off this filter; the rule itself is kept.
The rules are shown in priority order, lowest number first, which is the order the gateway evaluates them in; the first match routes the request. To change the order, change the rules' Priority. The filter must grant every target and fallback of its rules on the Models tab, or it does not save. Endpoint and Browser filters have no Routing tab. See Routing Rules.
Guardrails
The Guardrails tab is the same for both filter types. It lists the guardrails the filter binds.

- Browse Guardrails picks existing guardrails.
- New Guardrail opens the guardrail editor and binds the new rule to this filter.
- The menu on each row edits or removes it.
Guardrails are optional. A gateway filter without guardrails grants its models, limits and MCP servers but inspects nothing, and an endpoint filter without guardrails enforces nothing. A rule in report mode is a useful minimum.
Name

Enter the Name of the Filter and an optional Description, then click Add Filter, or Save Changes when you edit. Creating, updating and deleting a filter are recorded in Activity > Events.
Design patterns
| Goal | Filter |
|---|---|
| Visibility first on devices | Endpoint; group All; every OS; Agents = the AI apps in use; guardrails in report mode |
| Developers with IDE agents | Endpoint; group developers; Agents: Cursor, VS Code, Claude Desktop; secret and personal-data guardrails in block mode |
| AI use in the browser | Endpoint; the users' group; OS Browser; personal-data redaction and prompt-injection block |
| Servers and agents enrolled with setup keys | Endpoint; the setup key's auto-group; OS Linux (hooks or SDK) |
| Everyone may use approved models through the gateway | Gateway; group All; Models = the approved models; Gateways = the published address; a monthly spend limit; baseline guardrails |
| A team that gets more | A second gateway filter for its group with the extra models and MCP servers. Grants add up, but the lowest limit still wins, so keep the baseline's limit generous or leave it off the baseline |
Keep one baseline filter for All and add group-specific filters on top. Remember that a rule bound in the baseline reaches everyone; to exempt a group from a rule, the rule must not be in any filter that matches that group.
Delete a filter
Open the row's Delete action and confirm. Deleting a filter stops what it bound or granted: its devices drop its guardrails, and its gateway users lose its grants at the gateway's next check.
Troubleshooting
A device records nothing.
- The device is in one of the filter's groups and runs one of its operating systems. Check the device's groups under Endpoint > Peers.
- The filter is enabled and of type Endpoint.
- The client is connected and has the filter: after each change its log shows
Filters applied: N.Failed rules: [<id>]names guardrails that did not parse. - The traffic reaches the client: on Windows and macOS the app's path is in Agents; on Linux, hooks, the SDK or the proxy settings are in place.
Chrome is not intercepted although it is in Agents. The path does not match the install, for
example a per-user install under %LocalAppData%. Add both variants.
A Browser filter does not apply. The OS list must contain Browser; the user must be in one of the filter's groups and signed in to the extension; and the extension must not have stood down for the desktop client (its popup says so). After a change, press Refresh in the extension's popup. See Browser Extension.
Gateway users are refused every model. The user is in none of the filter's groups, the filter grants no model, or the provider or model is disabled.
The Workplace shows no gateway although the models work. The Gateways tab is empty. Continue skips it; open it and add the address.
A user gets more than intended. Another filter, often a baseline for All, grants it too. Grants add up.
A user gets less than intended. Another filter carries a lower limit.
The filter does not save, naming a routing rule. The filter does not grant a target or fallback of one of its routing rules. Grant the model on the Models tab, or All models of the provider for a rule that keeps the requested model. See Routing Rules.
The filter does not save. A required field is empty (group, operating system for an endpoint filter, model for a gateway filter), or a guardrail it names was deleted through the API; remove it from the filter.
A group cannot be deleted. A filter still targets it. Edit the filter first.
Related Documentation
- Guardrails - the rules a filter binds
- Providers - the models a gateway filter grants
- Limits - per-user spend and rate limits
- MCP - MCP servers and bundles a gateway filter grants
- Routing Rules - send a gateway filter's requests to other providers and models
- AI Gateway - the gateway that enforces gateway filters
- Browser Extension - how Browser filters reach the extension
- General-Purpose Agents - choosing Agents paths for desktop apps
- Agentic Access - what users see for their gateway filters

