Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
MCPpedia last refreshed this data
io.github.Runewardd/runeward is an MCP server that governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-runewardd-runeward": {
"args": [
"-y",
"@runeward/sdk"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@runeward/sdk' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @runeward/sdk against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in developer-tools / ai-ml
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP server for using the GitLab API
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Runewardd/runeward and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Rune Box: an environment where your agent can roam freely but with receipts.
The open-source governance harness for AI agents, by Runeward.
Put enforceable policy, human approvals, isolated execution, budgets, and signed evidence around any AI agent. Rune Box works with an existing agent or multi-agent framework rather than requiring a new model or orchestration stack.
Prerequisites: a running Docker, OrbStack, or Podman engine and the runebox binary.
runebox quickstart
The command creates .runebox/quickstart.toml, checks the policy, runtime, image, and state path,
runs an allowed command, proves a destructive command is denied before execution, and verifies the
signed audit trail. It never overwrites an existing policy unless --force is passed.
doctor and dashboard readiness also resolve required secret sources. A Charter that references an
unset env:// value is not presented as launch-ready.
runebox doctor quickstart # explain setup problems safely
runebox --config-dir .runebox serve # dashboard + governed REST API
runebox evidence export quickstart -o run.json
runebox evidence verify run.json # independent policy/audit verification
| Concern | Container alone | Rune Box |
|---|---|---|
| Tool calls | Executes what the process requests | Checks every shell, code, file, network, and browser action first |
| Risky actions | Application-specific | allow, deny, or require-approval with an attributed decision |
| Network | Usually open unless separately configured | Deny-by-default hostname policy; strict L3 enforcement on Kubernetes |
| Limits | CPU/memory | Wall-clock, exec, egress, token, cost, and retry-loop budgets |
| Audit | Runtime logs | Append-only, hash-chained, Ed25519-signed events |
| Handoff | Ad-hoc logs and folders | Workspace tar, recovery snapshots, and portable signed evidence JSON |
| Agent identity | One opaque process | Tenant, actor, parent run, provider, model, and durable run lineage |
| Interfaces | Runtime-specific | CLI, REST, MCP, web dashboard, Kubernetes CRDs, and local SDK adapters |
Every governed action follows one path:
agent request → policy → human approval when required → limits → sandbox → signed audit event
Documentation and UI use familiar terms first. Existing API paths and file fields retain the original themed names for compatibility.
| Plain-language term | Rune Box name | Existing surface |
|---|---|---|
| Sandbox | Citadel | /v1/citadels, Kubernetes Citadel |
| Policy file/profile | Charter | /v1/charters, *.toml profile |
| Approvals | Conclave | /v1/conclave |
| Signed audit trail | Chronicle | /v1/chronicle, [chronicle] |
| Network controls | Perimeter | /perimeter, [network] |
| Budgets and limits | Rationing | [rationing] |