You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: File system permissions for MCP servers running in Docker containers #275
For MCP servers running in docker containers using the container: syntax, we need a way to grant file system access via volume mounting. You should design a new syntax that allows the frontmatter in the markdown to epxress
Summary: This issue requests implementing filesystem permissions for MCP servers running in Docker containers, enabling secure volume mounting through a new frontmatter syntax for storage permissions.
📋 Implementation Analysis
Key Requirements:
Design new frontmatter syntax for filesystem permissions (permissions.storage.allow)
Support fs:// URIs with read/write access controls
Compile permissions to Docker volume mounts in GitHub Actions YAML
Integrate with existing container: syntax for MCP servers
Related Work:
🔗 Issue githubnext/gh-aw-internal#546: Unix-style read/write permissions for containers (similar scope)
Priority: High - This is foundational security infrastructure for the MCP ecosystem, enabling safe filesystem access patterns for containerized agents.
AI-generated content by Agentic Triage may contain mistakes.
changed the title [-]File system permissions for MCP servers running in Docker containers[/-][+]Proposal: File system permissions for MCP servers running in Docker containers[/+]on Aug 14, 2025
👋 Assigned to @Mossaka based on your expertise with MCP server container configurations and security features. This issue aligns with your work on container security proposals (#90, github/gh-aw#175).
I've analyzed the Auto-Assign workflow and identified the problem you mentioned. The workflow was repeatedly assigning people to issues that already had assignees.
Problem Found
Issue #275 already has 4 assignees (Mossaka, mnkiefer, lpcox, Copilot), but the Auto-Assign workflow kept assigning more people to it on:
Dec 20, 19, 18, 17, 14, 13, and Dec 4
The workflow instructions said "Find ONE open issue that has no assignees" but this was ambiguous - the AI wasn't properly checking if the assignees array was empty.
Fix Applied
I've created a pull request that makes the instructions explicit:
Changed to: "Has no assignees (verify the assignees array is empty)"
Added: "Critical: Before assigning, double-check the issue has zero assignees. Skip issues that already have one or more assignees."
This ensures the agent will:
Actually check the assignees array field
Understand zero means completely empty
Skip any issues with existing assignees
Pull Request
The fix is ready for review in the automatically created PR. The workflow has been validated and compiles successfully.
Assigned to @Mossaka as the original author of this proposal. This is the oldest unassigned issue in the repository (opened Aug 14, 2025) regarding file system permissions for MCP servers in Docker containers.
Assigning this to you @Mossaka since you opened it and have expertise in MCP server architecture. This is the oldest unassigned issue in the backlog and would benefit from your design input on the storage permissions syntax.
Assigned to @pelikhan based on recent activity with MCP server configuration and security features. This issue aligns with ongoing work on container permissions and MCP server hardening.
Assigned to @mnkiefer based on recent contributions to the repository including work on workflow health management, schema validation, and security fixes.
Assigning to @mnkiefer based on recent contributions to schema validation, container configuration, and infrastructure improvements. This issue involves designing a new syntax for MCP server file system permissions with Docker volume mounts.
Assigning to @pelikhan based on recent contributions to MCP server and Docker filesystem features. This issue aligns well with your recent work in this area.
👋 Hi @Mossaka! This issue about filesystem permissions for MCP servers running in Docker containers seems aligned with your recent work on container-related features. Assigning this to you for investigation.
Activity
github-actions commentedon Aug 14, 2025
🎯 Agentic Issue Triage
Summary: This issue requests implementing filesystem permissions for MCP servers running in Docker containers, enabling secure volume mounting through a new frontmatter syntax for storage permissions.
📋 Implementation Analysis
Key Requirements:
permissions.storage.allow)fs://URIs with read/write access controlscontainer:syntax for MCP serversRelated Work:
Architecture Impact:
pkg/parser/mcp.go: Extend MCPServerConfig with filesystem permissionspkg/workflow/compiler.go: Generate Docker volume mount configurations🔧 Implementation Strategy
Development Checklist:
permissions.storagesectionTechnical Considerations:
🔒 Security Implications
Security Priorities:
Best Practices:
📚 Resources & References
Docker Documentation:
GitHub Actions:
Related Codebase Files:
pkg/parser/mcp.go- MCP configuration parsingpkg/workflow/compiler.go- Workflow compilation logicCLAUDE.md- Project development guidelinesPriority: High - This is foundational security infrastructure for the MCP ecosystem, enabling safe filesystem access patterns for containerized agents.
[-]File system permissions for MCP servers running in Docker containers[/-][+]Proposal: File system permissions for MCP servers running in Docker containers[/+]missing tool logs support (#461)
github-actions commentedon Dec 4, 2025
Assigning to
@Mossakaas this relates to MCP server Docker container permissions, an area where you have expertise based on your related proposals (#90, github/gh-aw#175, github/gh-aw#1056, github/gh-aw#3175).github-actions commentedon Dec 13, 2025
Assigned to
@pelikhanbased on recent contributions to MCP-related features and Docker integration work in the repository.github-actions commentedon Dec 14, 2025
👋 Assigned to
@Mossakabased on your expertise with MCP server container configurations and security features. This issue aligns with your work on container security proposals (#90, github/gh-aw#175).7 remaining items
github-actions commentedon Dec 20, 2025
✅ Q Investigation Complete
I've analyzed the Auto-Assign workflow and identified the problem you mentioned. The workflow was repeatedly assigning people to issues that already had assignees.
Problem Found
Issue #275 already has 4 assignees (Mossaka, mnkiefer, lpcox, Copilot), but the Auto-Assign workflow kept assigning more people to it on:
The workflow instructions said "Find ONE open issue that has no assignees" but this was ambiguous - the AI wasn't properly checking if the
assigneesarray was empty.Fix Applied
I've created a pull request that makes the instructions explicit:
assigneesarray is empty)"This ensures the agent will:
assigneesarray fieldPull Request
The fix is ready for review in the automatically created PR. The workflow has been validated and compiles successfully.
github-actions commentedon Dec 21, 2025
Assigned to
@Mossakaas the original author of this proposal. This is the oldest unassigned issue in the repository (opened Aug 14, 2025) regarding file system permissions for MCP servers in Docker containers.github-actions commentedon Dec 24, 2025
Assigning this to you
@Mossakasince you opened it and have expertise in MCP server architecture. This is the oldest unassigned issue in the backlog and would benefit from your design input on the storage permissions syntax.github-actions commentedon Dec 25, 2025
Assigned to
@pelikhanbased on recent activity with MCP server configuration and security features. This issue aligns with ongoing work on container permissions and MCP server hardening.github-actions commentedon Dec 27, 2025
Assigned to
@mnkieferbased on recent contributions to the repository including work on workflow health management, schema validation, and security fixes.github-actions commentedon Dec 30, 2025
Assigning to
@mnkieferbased on recent contributions to schema validation, container configuration, and infrastructure improvements. This issue involves designing a new syntax for MCP server file system permissions with Docker volume mounts.github-actions commentedon Jan 1, 2026
Assigning to
@pelikhanas a highly active contributor who can help move this MCP server file system permissions proposal forward.github-actions commentedon Jan 2, 2026
Assigning to
@pelikhanbased on recent contributions to MCP server and Docker filesystem features. This issue aligns well with your recent work in this area.github-actions commentedon Jan 8, 2026
👋 Hi @Mossaka! This issue about filesystem permissions for MCP servers running in Docker containers seems aligned with your recent work on container-related features. Assigning this to you for investigation.