Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

MCP server must dynamically reload runtime profiles and capability gates or support hot restart #420

New Issue
Closed
opened 2026-07-07 10:57:50 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-07 10:57:50 -05:00
Owner
Copy Link
Copy Source

Problem

During review/merge runs, newly merged security/capability gates (such as the branch-delete gate in PR #410/Issue #408) do not immediately take effect in the active Gitea MCP server because the server runs in-memory and does not dynamically reload the code or profiles when master changes. This allows subsequent reviewer/audit sessions to execute mutations (like remote branch deletions) that should be forbidden under the updated codebase.

Hot-swapping or reloading is needed so that the server remains in parity with the master branch.

Required behavior

The Gitea MCP server must reload or hot-restart when Master branch is updated, or it must dynamically load capability gates and execution profiles from the workspace files at tool invocation time, rather than caching them statically in memory.

Acceptance criteria

  1. MCP server has a file-watcher or reload trigger when master updates.
  2. In-memory profile allowed_operations list is read dynamically or refreshed upon config file changes.
  3. Mutations check the current codebase's capability gates at runtime.
  4. Added test cases for dynamic reload.
## Problem During review/merge runs, newly merged security/capability gates (such as the branch-delete gate in PR #410/Issue #408) do not immediately take effect in the active Gitea MCP server because the server runs in-memory and does not dynamically reload the code or profiles when master changes. This allows subsequent reviewer/audit sessions to execute mutations (like remote branch deletions) that should be forbidden under the updated codebase. Hot-swapping or reloading is needed so that the server remains in parity with the master branch. ## Required behavior The Gitea MCP server must reload or hot-restart when Master branch is updated, or it must dynamically load capability gates and execution profiles from the workspace files at tool invocation time, rather than caching them statically in memory. ## Acceptance criteria 1. MCP server has a file-watcher or reload trigger when `master` updates. 2. In-memory profile allowed_operations list is read dynamically or refreshed upon config file changes. 3. Mutations check the current codebase's capability gates at runtime. 4. Added test cases for dynamic reload.
sysadmin commented 2026-07-07 10:58:50 -05:00
Owner
Copy Link
Copy Source

Clarification on safety requirements for Issue #420:

This is not just a file-watcher feature. The core requirement is runtime safety proof:

  • Expose version/SHA: The MCP runtime must expose the active server code/profile/config version or SHA.
  • Gate awareness: Safety-gated tools must know whether the live runtime includes the merged gate.
  • Restart/reload proof: After merging a safety-critical gate, workflows must require runtime restart/reload proof before relying on the new protection.
  • Fail closed: If the runtime is stale, affected tools should fail closed or emit a hard warning.
  • Acceptable strategies: Dynamic reload, hot restart, or explicit restart verification are all acceptable implementation strategies to satisfy this proof requirement.
Clarification on safety requirements for Issue #420: This is not just a file-watcher feature. The core requirement is runtime safety proof: * **Expose version/SHA**: The MCP runtime must expose the active server code/profile/config version or SHA. * **Gate awareness**: Safety-gated tools must know whether the live runtime includes the merged gate. * **Restart/reload proof**: After merging a safety-critical gate, workflows must require runtime restart/reload proof before relying on the new protection. * **Fail closed**: If the runtime is stale, affected tools should fail closed or emit a hard warning. * **Acceptable strategies**: Dynamic reload, hot restart, or explicit restart verification are all acceptable implementation strategies to satisfy this proof requirement.
jcwalker3 added the status:in-progress label 2026-07-07 12:04:37 -05:00
jcwalker3 commented 2026-07-07 12:04:37 -05:00
Author
Owner
Copy Link
Copy Source

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #420 - branch: feat/issue-420-master-parity-gate - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
sysadmin removed the status:in-progress label 2026-07-08 22:49:35 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#420