Cloudflare container MCP server and Dome
Let agents run code, and decide which ones and for how long. Cloudflare hosts an MCP server that gives an agent its own container to run commands and edit files in. Connect it to Dome once, and rules decide which agents may execute and how long a command may run. Every command lands in one audit trail.
Dome provides a governed gatewayfor Cloudflare Containers.
Execution decided per agent
Rules name the agents that may run commands in a container, and the rest get file reads or nothing.
A ceiling on every command
Rules read the timeout on each container_exec call. A command with no timeout, or one over a minute, is refused.
Each command on the record
Audit records every command, file write and refusal under the agent that made it. One trail covers code, tools and models.
Cloudflare containers behind the Gatewayin three steps.
Add the hosted server, sign in and sync its tools, and apply the rules. Dome registers its own OAuth client with Cloudflare.
Add the container MCP server
Credentials are per user, through Cloudflare OAuth. Each container belongs to the account that signed in.
shelldome tools add --name cloudflare-containers \ --url https://containers.mcp.cloudflare.com/mcp \ --auth-method oauth --credential-type per-user \ --oauth-authorize-url https://containers.mcp.cloudflare.com/oauth/authorize \ --oauth-token-url https://containers.mcp.cloudflare.com/token \ --oauth-registration-url https://containers.mcp.cloudflare.com/register \ --gateway compute-gatewaySync the catalog
Sync spends your own Cloudflare credential, so sign in first. Until then it fails and agents get “tool not available in this gateway”.
shelldome tools catalog sync cloudflare-containersApply the rules
Scope them to one agent while you try them, and simulate before you deploy.
shelldome rules apply cloudflare-exec.cedar \ --agent data-analyst --name cloudflare-exec
Run commands,one minute at a time.
The permit opens five container tools to the agent. The first forbid refuses every other tool, file deletes included, and the second refuses any command without a timeout of 60 seconds or less.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "cloudflare-containers" && ["container_initialize", "container_exec", "container_file_write", "container_file_read", "container_files_list"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "cloudflare-containers" && !["container_initialize", "container_exec", "container_file_write", "container_file_read", "container_files_list"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "cloudflare-containers" && resource.tool_name == "container_exec" && !(resource has arguments && resource.arguments has timeout && resource.arguments.timeout <= 60000)};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Timeout
agent data-analyst · acting as m.okafor
cloudflare-containers/container_exec(args: "python3 churn.py", timeout: 30000)
- Agentdata-analyst is registered and active
- Toolcontainer_exec is open to data-analyst
- RuleTimeout is 60 seconds or less
DecisionAllowed
Three agentson Cloudflare containers.
Each one gets the container tools its job needs, and only two of them may run commands.
data-analyst
Analyze exports
Writes a CSV export into its container, runs a Python script over it, and reads back the result, with each command stopping within a minute.
test-runner
Run a test suite
Starts a fresh container, writes the files under test and runs the suite. Results go back to the engineer who asked.
report-writer
Read results
Lists and reads the files other runs left behind and drafts a summary, without ever executing a command.
Bringing it alltogether.
Connecting Cloudflare Containers to registered agents, models, and identity in Dome completes a governed agent application.
Acting for
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Cloudflare ContainersAgent service
GitHubMCP serverModels
Common questionsabout Cloudflare Containers.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
Atlassian
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime
OpenAI Agents SDK
OpenAI Agents SDK agents with their models on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
Agent services: web, research, payments, voice and sandboxes
Web actions, research, payments, phone calls and code execution are where agents reach past your walls. Put each service behind the Gateway, and every call is authorized, metered and audited.