hugocasaandClaude Opus 5 deccd6538d fix: don't guess the MCP URL policy, and say where the switch lands on restart ...

Review findings:

The comment on the settings load claimed `MODE=mcp` as the target deployment, but
that mode joins no monitor loop, so the startup pass is its only read and a change
lands on restart. That is true of every global setting there, `base_url` included;
the comment now says so, and the setting description tells an operator running
dedicated MCP servers what to expect.

A failed settings probe resolved to "tokens allowed", so with the switch on the
drawer would mint a non-expiring token and hand over a URL the server refuses for
as long as it exists. The probe now propagates its error and the panel reports it
with a retry, creating nothing until the answer is known.

The test passed a valid token, so it could not tell a rejection before
authentication from one after it. It now also sends a token that was never valid
and asserts the middleware's own message, which fails if the layer moves inward.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-16 10:44:20 +02:00

..

cgroups.rs

fix: improve OOM killer observability for debugging pod-level kills (#8398)

2026-03-17 00:49:21 +00:00

db_connect.rs

feat(db-health): add connection sizing guidance (#10014)

2026-07-08 16:42:39 +00:00

ee_oss.rs

feat: export audit logs to a dedicated object store folder (#9207)

2026-05-19 14:43:54 +00:00

main.rs

feat: add an instance setting to refuse a token in MCP URLs

2026-09-16 10:29:21 +02:00

monitor.rs

fix: don't guess the MCP URL policy, and say where the switch lands on restart

2026-09-16 10:44:20 +02:00