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
| approval_retention_days | integer | Days to retain decided approvals before cleanup |
97
+
98
+
65
99
## AuthenticationConfiguration
66
100
67
101
@@ -205,6 +239,7 @@ Global service configuration.
205
239
| inference || One LLM provider and one its model might be selected as default ones. When no provider+model pair is specified in REST API calls (query endpoints), the default provider and model are used. |
206
240
| conversation_cache |||
207
241
| compaction || Controls when conversation history is summarized to keep the model's input below the context window limit. Disabled by default — when disabled, requests that exceed the window continue to surface as HTTP 413. |
242
+
| approvals || Settings for human-in-the-loop approval of MCP tool invocations |
208
243
| byok_rag | array | BYOK RAG configuration. This configuration can be used to reconfigure Llama Stack through its run.yaml configuration file |
209
244
| a2a_state || Configuration for A2A protocol persistent state storage. |
| authorization_headers | object | Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path. |
421
456
| headers | array | List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS. |
457
+
| require_approval | string or object | When to require human approval for MCP tool invocations. 'always' requires approval for all tools, 'never' auto-approves all tools (default), or use an ApprovalFilter for granular per-tool control. |
422
458
| timeout | integer | Timeout in seconds for requests to the MCP server. If not specified, the default timeout from Llama Stack will be used. Note: This field is reserved for future use when Llama Stack adds timeout support. |
Copy file name to clipboardExpand all lines: docs/openapi.json
+70-2Lines changed: 70 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -11400,7 +11400,7 @@
11400
11400
"title": "AllowedToolsFilter",
11401
11401
"description": "Filter configuration for restricting which MCP tools can be used.\n\n:param tool_names: (Optional) List of specific tool names that are allowed"
11402
11402
},
11403
-
"ApprovalFilter": {
11403
+
"ApprovalFilter-Input": {
11404
11404
"properties": {
11405
11405
"always": {
11406
11406
"anyOf": [
@@ -11435,6 +11435,52 @@
11435
11435
"title": "ApprovalFilter",
11436
11436
"description": "Filter configuration for MCP tool approval requirements.\n\n:param always: (Optional) List of tool names that always require approval\n:param never: (Optional) List of tool names that never require approval"
11437
11437
},
11438
+
"ApprovalFilter-Output": {
11439
+
"properties": {
11440
+
"always": {
11441
+
"items": {
11442
+
"type": "string"
11443
+
},
11444
+
"type": "array",
11445
+
"title": "Always require approval",
11446
+
"description": "List of tool names that always require human approval"
11447
+
},
11448
+
"never": {
11449
+
"items": {
11450
+
"type": "string"
11451
+
},
11452
+
"type": "array",
11453
+
"title": "Never require approval",
11454
+
"description": "List of tool names that never require approval"
11455
+
}
11456
+
},
11457
+
"additionalProperties": false,
11458
+
"type": "object",
11459
+
"title": "ApprovalFilter",
11460
+
"description": "Granular approval control for specific MCP tools.\n\nAttributes:\n always: Tool names that always require human approval before execution.\n never: Tool names that never require approval (pre-approved)."
11461
+
},
11462
+
"ApprovalsConfiguration": {
11463
+
"properties": {
11464
+
"approval_timeout_seconds": {
11465
+
"type": "integer",
11466
+
"exclusiveMinimum": 0.0,
11467
+
"title": "Approval timeout",
11468
+
"description": "Seconds before pending approval requests expire",
11469
+
"default": 300
11470
+
},
11471
+
"approval_retention_days": {
11472
+
"type": "integer",
11473
+
"exclusiveMinimum": 0.0,
11474
+
"title": "Retention period",
11475
+
"description": "Days to retain decided approvals before cleanup",
11476
+
"default": 30
11477
+
}
11478
+
},
11479
+
"additionalProperties": false,
11480
+
"type": "object",
11481
+
"title": "ApprovalsConfiguration",
11482
+
"description": "Configuration for human-in-the-loop approvals.\n\nAttributes:\n approval_timeout_seconds: How long approval requests remain pending\n before expiring.\n approval_retention_days: How long to retain decided approvals for audit\n purposes before cleanup."
11483
+
},
11438
11484
"Attachment": {
11439
11485
"properties": {
11440
11486
"attachment_type": {
@@ -12016,6 +12062,11 @@
12016
12062
"title": "Conversation compaction configuration",
12017
12063
"description": "Controls when conversation history is summarized to keep the model's input below the context window limit. Disabled by default \u2014 when disabled, requests that exceed the window continue to surface as HTTP 413."
"description": "Settings for human-in-the-loop approval of MCP tool invocations"
12069
+
},
12019
12070
"byok_rag": {
12020
12071
"items": {
12021
12072
"$ref": "#/components/schemas/ByokRag"
@@ -14264,6 +14315,23 @@
14264
14315
"title": "Propagated headers",
14265
14316
"description": "List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS."
"description": "When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control.",
0 commit comments