Cloudflare container MCP server and Dome

1. 01

   Add the container MCP server

   Credentials are per user, through Cloudflare OAuth. Each container belongs to the account that signed in.

   $ dome 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-gateway

2. 02

   Sync 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”.

   $ dome tools catalog sync cloudflare-containers

3. 03

   Apply the rules

   Scope them to one agent while you try them. Simulate before you deploy.

   $ dome rules apply cloudflare-exec.cedar \
     --agent data-analyst --name cloudflare-exec

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Cloudflare Containers itself, see Cloudflare's documentation.

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)
};