Skip to content

NimBus v4.6.0

Choose a tag to compare

@akakaule akakaule released this 07 Oct 08:31
· 56 commits to master since this release
0f3b02e

NimBus 4.6.0 adds an Admin tab where site Owners can turn the operator MCP endpoint off and narrow what AI agents may do, without a redeploy or an Entra change.

Highlights

  • Added Admin → MCP access, where a site Owner can switch the /mcp endpoint on and off and turn off payloads, report, classify, resubmit and skip for agents. They can also restrict which workloads, people, client apps and endpoints agents may reach, and lower the rate limits. Before saving, a review step marks each change as widening or narrowing access, and Turn off now disables the endpoint at once.
  • Added an effective-access preview, connection instructions and recent MCP activity to the tab. Switched-off tools disappear from tools/list and permittedActions, and refused calls are audited as McpAccessRefused.
  • Fixed nimbus_classify_failure accepting an attempt that belongs to another endpoint, and it now re-checks the Contributor role against fresh access-control lists before classifying.

Compatibility

IEndpointMetadataStore adds GetMcpAccessSettings and TrySetMcpAccessSettings without default implementations, so custom implementations must add them; the Cosmos DB, SQL Server and in-memory stores already do. SQL Server applies migration 0023_McpAccessSettings on startup; with VerifyOnly, run it from your pipeline first. Cosmos DB stores the policy in the existing settings container, so no nb infra apply is needed. MessageAuditType adds UpdateMcpSettings and McpAccessRefused, which are always recorded.

The WebApp adds GET/PUT /api/admin/mcp/settings, POST /api/admin/mcp/turn-off and GET /api/admin/mcp/activity, all for site Owners only. The deployment settings (NimBus__Mcp__*, the Entra registration and the rate-limit maxima) remain the ceiling, and the Admin policy can only narrow it. Until a policy is saved, MCP behaves as in 4.5.0. Once a policy turns the endpoint off, /mcp answers 503 [Disabled]; if the policy cannot be read at startup, it answers 503 [Unavailable]. No topology change or wire change.

This release was validated at commit 0f3b02e with the full .NET Release build and 3,629 tests in CI (2 skipped), live Cosmos DB and SQL Server conformance suites with no skipped tests, and Service Bus emulator compatibility checks. The frontend production build passed against the release commit's sources; in the full frontend run, 568 of 569 tests passed, and the one timeout came from a Failed-page test that is flaky under load, unchanged since 4.5.0, and passes when its file runs alone. The Admin policy has not yet been piloted against a real Entra deployment.

PRs: #214, #215, #216

Commits: v4.5.0...v4.6.0