You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MCPClientConnectionEstablishTimeout=30*time.Second// Timeout for MCP client connection establishment
24
-
25
-
// Context keys for client filtering in requests
26
-
// NOTE: []string is used for both keys, and by default all clients/tools are included (when nil).
27
-
// If "*" is present, all clients/tools are included, and [] means no clients/tools are included.
28
-
// Request context filtering takes priority over client config - context can override client exclusions.
29
-
MCPContextKeyIncludeClients schemas.BifrostContextKey="mcp-include-clients"// Context key for whitelist client filtering
30
-
MCPContextKeyIncludeTools schemas.BifrostContextKey="mcp-include-tools"// Context key for whitelist tool filtering (Note: toolName should be in "clientName-toolName" format for individual tools, or "clientName-*" for wildcard)
// NOTE: []string is used for both keys, and by default all clients/tools are included (when nil).
162
+
// If "*" is present, all clients/tools are included, and [] means no clients/tools are included.
163
+
// Request context filtering takes priority over client config - context can override client exclusions.
164
+
MCPContextKeyIncludeClientsBifrostContextKey="mcp-include-clients"// Context key for whitelist client filtering
165
+
MCPContextKeyIncludeToolsBifrostContextKey="mcp-include-tools"// Context key for whitelist tool filtering (Note: toolName should be in "clientName-toolName" format for individual tools, or "clientName-*" for wildcard)
166
+
160
167
BifrostContextKeySelectedKeyIDBifrostContextKey="bifrost-selected-key-id"// string (to store the selected key ID (set by bifrost governance plugin - DO NOT SET THIS MANUALLY))
161
168
BifrostContextKeySelectedKeyNameBifrostContextKey="bifrost-selected-key-name"// string (to store the selected key name (set by bifrost governance plugin - DO NOT SET THIS MANUALLY))
162
169
BifrostContextKeyGovernanceVirtualKeyIDBifrostContextKey="bifrost-governance-virtual-key-id"// string (to store the virtual key ID (set by bifrost governance plugin - DO NOT SET THIS MANUALLY))
BifrostContextKeyIsAzureUserAgentBifrostContextKey="bifrost-is-azure-user-agent"// bool (set by bifrost - DO NOT SET THIS MANUALLY)) - whether the request is an Azure user agent (only used in gateway)
221
+
BifrostContextKeyIsAzureUserAgentBifrostContextKey="bifrost-is-azure-user-agent"// bool (set by bifrost - DO NOT SET THIS MANUALLY)) - whether the request is an Azure user agent (only used in gateway)
BifrostContextKeyValidateKeysBifrostContextKey="bifrost-validate-keys"// bool (triggers additional key validation during provider add/update)
223
+
BifrostContextKeyValidateKeysBifrostContextKey="bifrost-validate-keys"// bool (triggers additional key validation during provider add/update)
217
224
BifrostContextKeyProviderResponseHeadersBifrostContextKey="bifrost-provider-response-headers"// map[string]string (set by provider handlers for response header forwarding)
218
225
)
219
226
@@ -891,4 +898,3 @@ type BifrostErrorExtraFields struct {
Copy file name to clipboardExpand all lines: docs/features/governance/routing.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ This powerful feature enables key use cases like:
28
28
Virtual Keys can be restricted to use only specific provider/models. When provider/model restrictions are configured, the VK can only access those designated provider/models, providing fine-grained control over which provider/models different users or applications can utilize.
29
29
30
30
**How It Works:**
31
-
-**No Restrictions** (default): VK can use any available provider/models based on global configuration
32
-
-**With Restrictions**: VK limited to only the specified provider/models with weighted load balancing
31
+
-**No Provider Configs** (default): VK **blocks all providers** (deny-by-default). You must add provider configurations to allow traffic.
32
+
-**With Provider Configs**: VK limited to only the specified provider/models with weighted load balancing
33
33
34
34
**Model Validation:**
35
35
When you configure provider restrictions on a Virtual Key, Bifrost validates that the requested model is allowed for the selected provider:
Copy file name to clipboardExpand all lines: docs/mcp/filtering.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,7 +227,7 @@ This consistent naming convention ensures clear separation between tools from di
227
227
Virtual Keys can have their own MCP tool access configuration, which **takes precedence** over request-level headers.
228
228
229
229
<Note>
230
-
When a Virtual Key has MCP configurations, it generates the `x-bf-mcp-include-tools` header automatically, overriding any manually sent header.
230
+
When a Virtual Key has no MCP configurations, **no MCP tools are available** (deny-by-default). You must explicitly add MCP client configurations to allow tools. When a Virtual Key has MCP configurations, it generates the `x-bf-mcp-include-tools` header automatically, overriding any manually sent header.
0 commit comments