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

Block role/tool namespace mismatch for author and reviewer mutations #209

New Issue
Closed
opened 2026-07-05 15:26:57 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-05 15:26:57 -05:00
Owner
Copy Link
Copy Source

Problem

Agents can perform author-side mutations through a reviewer MCP namespace or report one role while using tools from another namespace. This makes capability proofs unreliable and weakens role-boundary enforcement.

Observed failure

The transcript shows author mutations being performed with reviewer-prefixed tools:

  • gitea-reviewer/gitea_create_issue
  • gitea-reviewer/gitea_create_pr

But the final handoff reports:

  • Role: author
  • Identity: jcwalker3 / prgs-author

This is contradictory. A reviewer namespace should not be used for author mutations, and an author handoff must not rely on reviewer tool calls.

Required wall

Every mutation must prove that the tool namespace, active profile, authenticated username, and allowed capability all match the declared task role.

Acceptance criteria

  • Add a test where gitea-reviewer/gitea_create_issue is invoked; expected result: blocked unless reviewer profile explicitly allows issue creation for that task.
  • Add a test where gitea-reviewer/gitea_create_pr is invoked; expected result: blocked.
  • Add a test where the final handoff role does not match the mutation tool namespace; expected result: invalid handoff.
  • Add a test where capability proof says prgs-author but mutation path says gitea-reviewer; expected result: blocked.
  • Mutation audit logs must include namespace, profile, username, remote, repo, operation, and task role for every mutation.

Related issues

  • #139 - role-aware MCP task routing
  • #191 - issue-filing final reports and exact mutation capability proof
  • #197 - hard-stop purity after reviewer capability denial
  • #206 - pre-task role/session router
## Problem Agents can perform author-side mutations through a reviewer MCP namespace or report one role while using tools from another namespace. This makes capability proofs unreliable and weakens role-boundary enforcement. ## Observed failure The transcript shows author mutations being performed with reviewer-prefixed tools: * `gitea-reviewer/gitea_create_issue` * `gitea-reviewer/gitea_create_pr` But the final handoff reports: * `Role: author` * `Identity: jcwalker3 / prgs-author` This is contradictory. A reviewer namespace should not be used for author mutations, and an author handoff must not rely on reviewer tool calls. ## Required wall Every mutation must prove that the tool namespace, active profile, authenticated username, and allowed capability all match the declared task role. ## Acceptance criteria * Add a test where `gitea-reviewer/gitea_create_issue` is invoked; expected result: blocked unless reviewer profile explicitly allows issue creation for that task. * Add a test where `gitea-reviewer/gitea_create_pr` is invoked; expected result: blocked. * Add a test where the final handoff role does not match the mutation tool namespace; expected result: invalid handoff. * Add a test where capability proof says `prgs-author` but mutation path says `gitea-reviewer`; expected result: blocked. * Mutation audit logs must include namespace, profile, username, remote, repo, operation, and task role for every mutation. ## Related issues * #139 - role-aware MCP task routing * #191 - issue-filing final reports and exact mutation capability proof * #197 - hard-stop purity after reviewer capability denial * #206 - pre-task role/session router
jcwalker3 added the status:in-progress label 2026-07-05 20:11:40 -05:00
jcwalker3 commented 2026-07-05 20:13:01 -05:00
Author
Owner
Copy Link
Copy Source

Implementation pushed on branch feat/issue-209-namespace-mismatch.

PR: #223

Adds role_namespace_gate, wires namespace blocks into gitea_create_issue/gitea_create_pr, enriches mutation audit records (mcp_namespace, task_role, operation), and adds assess_mutation_namespace_handoff for invalid author handoffs that used gitea-reviewer.

20 targeted tests pass.

Implementation pushed on branch `feat/issue-209-namespace-mismatch`. **PR:** [#223](https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/pulls/223) Adds `role_namespace_gate`, wires namespace blocks into `gitea_create_issue`/`gitea_create_pr`, enriches mutation audit records (`mcp_namespace`, `task_role`, `operation`), and adds `assess_mutation_namespace_handoff` for invalid author handoffs that used `gitea-reviewer`. 20 targeted tests pass.
sysadmin removed the status:in-progress label 2026-07-06 00:14:50 -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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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