validate_config
Validate OIDC proxy config files: detect unknown keys, type errors, and invalid values in settings.yaml, users.yaml, and bootstrap.yaml before they cause startup or reload failures. Read-only operation.
Instructions
Validate the running configuration directory (settings.yaml, users.yaml, bootstrap.yaml): unknown keys as warnings, wrong types and refused values as errors. settings.yaml and users.yaml findings are what a startup or the next reload would hit; bootstrap.yaml findings are what would stop the NEXT startup (the bootstrap surface loads at startup only). Read-only and inert: it re-reads the files through the same loaders, runs no hook and loads no plugin. 'valid' is false on any error, and on a warning too under strict mode, which is when a start would refuse. 'strict' defaults to this server's effective validation mode; pass it explicitly to override.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "validate_config"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| strict | No | Treat warnings as failures, like the server's --strict-config. A directory declaring config_validation: strict is strict regardless. |