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

Enforce strict cross-project boundaries (permit issues, block codebase mutations) #707

New Issue
Open
opened 2026-07-13 21:15:04 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-13 21:15:04 -05:00
Owner
Copy Link
Copy Source

Problem

Currently, there is no strict boundary preventing an AI agent instantiated in one project context from executing codebase mutations (such as branch creation, file modification, or PR creation) against another distinct project repository. If the agent's filesystem or MCP permissions technically allow it, the agent can spontaneously attempt to perform direct code work outside of its originally authorized context.

While we want to enable agents to orchestrate cross-project coordination, this should be strictly confined to metadata operations (e.g., creating issues) rather than direct codebase modification.

Requirements

  1. Implement a policy/guard inside the MCP server that explicitly enforces cross-project mutation boundaries.
  2. Allow agents to execute metadata operations (such as creating tracking issues or commenting on issues) across project boundaries to coordinate workflows.
  3. Block any attempt to execute mutation operations (creating branches, committing files, creating PRs) outside of the primary authorized project context.
  4. Ensure clear diagnostic output when this boundary is hit, explicitly advising the agent that cross-project work is forbidden and that it should create an issue in the target repository instead.
  5. Provide regression tests validating that cross-project codebase mutations fail closed, while cross-project issue creation is allowed.
## Problem Currently, there is no strict boundary preventing an AI agent instantiated in one project context from executing codebase mutations (such as branch creation, file modification, or PR creation) against another distinct project repository. If the agent's filesystem or MCP permissions technically allow it, the agent can spontaneously attempt to perform direct code work outside of its originally authorized context. While we want to enable agents to orchestrate cross-project coordination, this should be strictly confined to metadata operations (e.g., creating issues) rather than direct codebase modification. ## Requirements 1. Implement a policy/guard inside the MCP server that explicitly enforces cross-project mutation boundaries. 2. Allow agents to execute metadata operations (such as creating tracking issues or commenting on issues) across project boundaries to coordinate workflows. 3. Block any attempt to execute mutation operations (creating branches, committing files, creating PRs) outside of the primary authorized project context. 4. Ensure clear diagnostic output when this boundary is hit, explicitly advising the agent that cross-project work is forbidden and that it should create an issue in the target repository instead. 5. Provide regression tests validating that cross-project codebase mutations fail closed, while cross-project issue creation is allowed.
jcwalker3 added the type:guardrailstatus:ready labels 2026-07-13 21:16:36 -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 status:ready type:guardrail
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#707