Skip to content

Proposal: File system permissions for MCP servers running in Docker containers #275

Closed

Description

@Mossaka

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

permissions:
  storage:
      allow:
      - uri: fs://tmp/mcp-filesystem
        access: [read]

The storage will take a list of allowed fs paths and compile them down into volume mounts for docker containers in the GitHub Action YAML files.

Activity

  1. github-actions commented on Aug 14, 2025

    @github-actions
    Contributor

    🎯 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:

    • 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:

    Architecture Impact:

    • pkg/parser/mcp.go: Extend MCPServerConfig with filesystem permissions
    • pkg/workflow/compiler.go: Generate Docker volume mount configurations
    • Schema updates for frontmatter validation
    • Integration with existing container orchestration
    🔧 Implementation Strategy

    Development Checklist:

    • Extend MCPServerConfig struct with filesystem permissions field
    • Update frontmatter parsing to handle permissions.storage section
    • Create volume mount generation functions for Docker containers
    • Update workflow compiler to integrate filesystem permissions
    • Add validation for filesystem paths and access modes
    • Create comprehensive tests for parsing and compilation
    • Update documentation and examples

    Technical Considerations:

    • Path validation and sanitization (security critical)
    • Support for multiple filesystem access modes (read, write, readwrite)
    • Docker volume mount syntax generation
    • Integration with GitHub Actions runner filesystem constraints
    • Error handling for invalid filesystem paths
    🔒 Security Implications

    Security Priorities:

    • Input validation for filesystem paths to prevent directory traversal
    • Access mode enforcement (read-only vs read-write)
    • Container isolation maintenance
    • Audit logging for filesystem access requests

    Best Practices:

    • Use allowlist approach (explicit permissions only)
    • Validate against known safe filesystem patterns
    • Consider implementing path canonicalization
    • Document security boundaries and limitations
    📚 Resources & References

    Docker Documentation:

    GitHub Actions:

    Related Codebase Files:

    • pkg/parser/mcp.go - MCP configuration parsing
    • pkg/workflow/compiler.go - Workflow compilation logic
    • CLAUDE.md - Project development guidelines

    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.

  2. 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
  3. transferred this issue fromon Aug 15, 2025
  4. added a commit that references this issue on Sep 5, 2025
  5. github-actions commented on Dec 4, 2025

    @github-actions
    Contributor

    Assigning to @Mossaka as 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).

    🏴‍☠️ Ahoy! This treasure was crafted by Auto-Assign Issue

  6. github-actions commented on Dec 13, 2025

    @github-actions
    Contributor

    Assigned to @pelikhan based on recent contributions to MCP-related features and Docker integration work in the repository.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  7. github-actions commented on Dec 14, 2025

    @github-actions
    Contributor

    👋 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).

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  8. assigned and unassigned on Dec 14, 2025
  9. 7 remaining items

  10. locked and limited conversation to collaborators on Dec 20, 2025
  11. unlocked this conversation on Dec 20, 2025
  12. github-actions commented on Dec 20, 2025

    @github-actions
    Contributor

    ✅ 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:

    • 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:

    1. Actually check the assignees array field
    2. Understand zero means completely empty
    3. 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.


    🔧 Q workflow optimization completed by run #20395925551

    🎩 Equipped by Q fer issue #275 🗺️

  13. github-actions commented on Dec 21, 2025

    @github-actions
    Contributor

    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.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  14. github-actions commented on Dec 24, 2025

    @github-actions
    Contributor

    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.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  15. github-actions commented on Dec 25, 2025

    @github-actions
    Contributor

    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.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  16. github-actions commented on Dec 27, 2025

    @github-actions
    Contributor

    Assigned to @mnkiefer based on recent contributions to the repository including work on workflow health management, schema validation, and security fixes.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  17. github-actions commented on Dec 30, 2025

    @github-actions
    Contributor

    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.

    Ahoy! This treasure was crafted by 🏴‍☠️ Auto-Assign Issue

  18. github-actions commented on Jan 1, 2026

    @github-actions
    Contributor

    Assigning to @pelikhan as a highly active contributor who can help move this MCP server file system permissions proposal forward.

    AI generated by Auto-Assign Issue

  19. github-actions commented on Jan 2, 2026

    @github-actions
    Contributor

    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.

    AI generated by Auto-Assign Issue

  20. github-actions commented on Jan 8, 2026

    @github-actions
    Contributor

    👋 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.

    AI generated by Auto-Assign Issue

  21. transferred this issue fromgithub/gh-awon Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions