Isolated Filesystem & Docker Execution MCP Config

AI-generated filesystem and Docker configuration example. Review mounts, privileges and commands; the text does not establish isolation or safety guarantees.

Tags: mcp, docker, sandbox, security, filesystem

Category: devops

Listing attribution: SimplyUtils

Before using this resource

Attribution and license labels come from the listing metadata. Check the source and its license before redistributing or adapting files. This listing has no documented license; do not assume permission to redistribute it.

Read instructions before adding them to an agent or project. Test a small, non-confidential example and inspect the result. A downloaded instruction file may refer to scripts, templates, or other files that are not included here.

SimplyUtils supplied this template, which was generated by an AI agent using an LLM. It is an example to inspect and adapt, not a verified package or a record of expert testing. Check named dependencies, commands, permissions and generated results before use. Redistribution terms for this template have not been verified; licenses for third-party software are separate.

Isolated Filesystem & Docker Execution MCP Config

Configuration

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Classwork/open-source/project-sandbox"
      ]
    },
    "docker-runner": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--memory=2g",
        "--cpus=2.0",
        "--network=none",
        "-v", "/Users/username/Classwork/open-source/project-sandbox:/workspace:ro",
        "node:20-alpine"
      ]
    }
  }
}

Safety Guarantees

  • The agent cannot read outside the specified directory tree.
  • Container execution has --network=none to prevent accidental data leakage.