agent-sandbox-platform
Connects the autonomous agent loop to OpenAI model providers for live model calls, enabling real AI agent interactions within the sandbox.
Agent Sandbox Platform
Distributed via GitHub Container Registry (
ghcr.io/sumitdalavi/agent-sandbox-platform:v0.2.0) and tagged GitHub Releases with Anchore SPDX 2.3 SBOM and SHA-256 digest attestation.
The Problem
Modern distributed systems and AI agents require robust operational scaffolding. Simple CRUD apps or mock loops fail when subjected to real-world edge cases, asynchronous boundaries, and security constraints.
Related MCP server: AgentMCP
The Solution
An isolated execution platform for AI agents. An agent is given a broken service and a bounded toolset inside a disposable sandbox. Every command passes through policy, risky actions need human approval, results are verified by independent tests, and the whole run leaves a sanitized evidence bundle.
Key Capabilities & Architectural Highlights
Model Context Protocol (MCP): Server integration for Glama.ai, Smithery.ai, Claude Desktop, and Cursor.
Non-root Execution: Ephemeral container execution (UID 1000) with ReadonlyRootfs and CapDrop ALL.
5-Second Hard Deadline: Guaranteed synchronous container purge on timeout or completion.
Full OCI Distribution: Published to GitHub Container Registry (GHCR).
๐ป Tech Stack
Container Registry:
ghcr.io/sumitdalavi/agent-sandbox-platform:v0.2.0Security & Attestation: Anchore SPDX 2.3 SBOM, SHA-256 Checksums
License: MIT Open Source
๐ Documentation Index
Architecture Specification โ System diagram, component contracts, and container distribution architecture.
Production Runbook โ Operational runbook, live execution commands, and verification recipes.
Demo Walkthrough โ Step-by-step interactive demonstration scenario.
Changelog โ Full version history following Keep a Changelog and SemVer.
๐ Quickstart & Installation
Option 1: Run with Docker Container (GHCR)
docker pull ghcr.io/sumitdalavi/agent-sandbox-platform:v0.2.0
docker run -d -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/sumitdalavi/agent-sandbox-platform:v0.2.0Option 2: Run as Model Context Protocol (MCP) Server
Available on Glama.ai and Smithery.ai:
# Smithery one-line install:
npx -y @smithery/cli install SumitDalavi/agent-sandbox-platform --client claude
# Local client spec (.mcp.json):
{
"mcpServers": {
"agent-sandbox": {
"command": "node",
"args": ["mcp-server.js"]
}
}
}Option 3: Local Developer Setup
# 1. Clone the repository
git clone https://github.com/SumitDalavi/agent-sandbox-platform.git
cd agent-sandbox-platform
# 2. Build and start
make setup
make dev๐ฎ Usage & Demo
See docs/DEMO_SCRIPT.md for the interactive walkthrough and verification steps.
Demo (3 minutes)
Start "Repair failing checkout service".
Watch the agent's actual diagnostic commands stream in.
See an unauthorized network request denied by policy.
Review the proposed diff and approve export.
See independent tests pass and the sandbox torn down.
โ Verification
Operational Verification
Check | Command | Expected |
Build |
| Dependencies install successfully |
Run |
| Services start without crashing |
Test |
| Behavioral test suite passes |
Cryptographic & Supply Chain Verification
To verify the authentic origin, integrity, and software composition of release artifacts:
# 1. Download Release Bundle & Checksums
gh release download v0.2.0 --repo SumitDalavi/agent-sandbox-platform --pattern "*.tar.gz" --pattern "checksums.txt"
# 2. Verify SHA-256 Digest
sha256sum -c checksums.txt
# 3. Inspect SPDX 2.3 Software Bill of Materials
gh release download v0.2.0 --repo SumitDalavi/agent-sandbox-platform --pattern "sbom.spdx.json"
cat sbom.spdx.json | jq .spdxVersionCapability Status
Capability | Status |
Sandbox lifecycle API (create/exec/snapshot/destroy) | Implemented |
Container backend (hardened) | Implemented |
MicroVM backend (Firecracker) | Planned (stretch; requires KVM host) |
Policy engine (allowlists, limits) | Implemented |
Agent loop with real model calls | Implemented |
Human approval gate | Implemented |
Independent verification | Implemented |
Evidence bundle + timeline UI | Implemented |
Optional decision layer (risk signal) | Implemented |
Decision benchmark | Implemented |
๐ Dual-Mode Execution: Live-First with Graceful Mock Fallback
This platform operates in Dual-Mode, dynamically selecting between live container execution and self-contained policy simulation based on environment variables:
Component | Environment Variable | Live Mode Behavior | Fallback Mode (Unset / Empty) |
Container Engine |
| Launches isolated ephemeral Alpine containers via | Activates behavioral policy simulation when Docker daemon is unavailable |
Authentication Gate |
| Enforces enterprise Bearer token validation for all sandbox endpoints | Defaults to |
Policy Enforcement |
| Ingests custom organizational command blacklist (comma-separated) | Enforces default safety tokens ( |
Agent Tool Client |
| Connects live autonomous agent loop to external model providers | Runs deterministic diagnostic test scripts against sandbox APIs |
๐จโ๐ป Author
Sumit Dalavi โ Senior DevSecOps / Platform Engineer
GitHub | LinkedIn
๐ License
This project is licensed under the MIT License. Copyright (c) 2026 Sumit Dalavi.
Available Tools
2 toolsexecute_in_sandboxA
Executes untrusted shell commands or code payloads inside an isolated, non-root ephemeral Docker container with strict CPU/memory limits and timeout enforcement.
Inputs: code (required), timeoutMs.
validate_sandbox_policyB
Evaluates a proposed command against security policy rules (e.g. denylist patterns, egress boundaries) before execution.
Inputs: command (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs a pre-execution policy check and the other actually runs the command in an isolated container. An agent can readily tell whether it needs validation or execution, and the descriptions reinforce the boundary.
Both names are snake_case and verb-led, giving a predictable feel. The patterns differ slightly (validate_noun vs. execute_in_noun), but they remain readable and consistent enough for reliable selection.
Two tools is thin for a platform that implies sandbox lifecycle management beyond validation and execution. The pair covers the minimal workflow, but the surface feels borderline sparse rather than well-scoped.
Core actionsโpolicy validation and isolated executionโare present, but obvious lifecycle operations such as sandbox status, cancellation, cleanup, or policy management are absent. Agents can work around some gaps because containers are ephemeral, but the surface is not fully complete for a sandbox platform.
Maintenance
Related MCP Connectors
Autonomous and governed SRE & MLOps control plane for AI agent platforms.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Run AI agent tasks in isolated sandboxes with a cost cap, saved workflows and scoped connections.
Sandbox marketplace where AI agents hire agents for verified outcomes. Test money only.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides isolated sandbox environments for AI agents to execute code securely, generating signed receipts for every execution to ensure auditability and trust.11 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to operate autonomously with safety, parallelism, and dynamic tool management, without giving them full machine access.1AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to run compute tasks in secure sandboxes with optional interactive UIs, brokering between agents and isolated execution environments.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and software engineers to investigate and resolve realistic distributed-system incidents using safe MCP-based diagnostic tools for code, logs, metrics, traces, database, and deployments.Apache 2.0