Announcing Dome Managed Agents.

Try it now

Apify MCP server and Dome

Put Apify's Actors to work, and decide which ones run on which sites. Apify runs Actors, ready-made scrapers and crawlers that agents call as tools. Connect Apify's hosted MCP server to Dome once, and rules decide each fetch on its URL and each run on the Actor it names. Every run lands in one audit trail.

Dome provides a governed gatewayfor Apify.

Fetches decided on the URL

Rules read the URL of every Web Fetch call. A listed site is fetched, and a lookalike domain is refused.

Actors decided by name

call-actor can start any Actor in the Apify Store. A rule on its actor argument keeps an agent to the ones you name.

One token, held by Dome

Dome holds the Apify API token and injects it on each call. Agents authenticate to the Gateway with their own Dome key.

Apify behind the Gatewayin three steps.

Add the hosted MCP server with the tools you want, sync them into the Gateway's catalog, and apply the rules. The tools parameter on the URL picks which tools Apify serves.
  1. Add the Apify MCP server

    This URL loads Web Fetch and call-actor. Dome stores the Apify token and sends it as a Bearer token.

    shell
    dome tools add --name apify \  --url "https://mcp.apify.com?tools=apify/web-fetch,call-actor" \  --auth-method api-key \  --credential-type shared \  --authorization "Bearer $APIFY_TOKEN" \  --gateway research-gateway
  2. Sync the catalog

    Sync needs a valid token, and Apify refuses the listing without one. Until it runs, agents get “tool not available in this gateway”.

    shell
    dome tools catalog sync apify
  3. Apply the rules

    Scope them to one agent while you try them, and simulate before you deploy.

    shell
    dome rules apply apify-permit.cedar apify-limits.cedar \  --agent filings-reader --name apify-limits

Fetch two sites,run one Actor.

The permit opens Web Fetch, call-actor and the run results to the agent. The first forbid refuses any fetch off two sites, and the second refuses any Actor but Google Search Scraper.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "apify" &&  ["apify--web-fetch", "call-actor", "get-actor-run", "get-dataset-items"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "apify" &&  resource.tool_name == "apify--web-fetch" &&  !(resource has arguments &&    resource.arguments has url &&    (resource.arguments.url like "https://www.sec.gov/*" ||     resource.arguments.url like "https://investors.northwind-supply.com/*"))};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "apify" &&  resource.tool_name == "call-actor" &&  !(resource has arguments &&    resource.arguments has actor &&    resource.arguments.actor == "apify/google-search-scraper")};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Site

agent filings-reader · scheduled
apify/apify--web-fetch(url: "https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0000320193")
  1. Agentfilings-reader is registered and active
  2. Rulewww.sec.gov is on the list
DecisionAllowed

Three agentson Apify.

Each one gets its own sites and Actors. A bundle per agent keeps one agent's list from widening another's.

filings-reader

Read SEC filings

Fetches new filings for the companies under review each morning, and is refused on any other site.

news-scanner

Scan search results for news

Runs Google Search Scraper for each vendor and hands the results to an analyst, and every other Actor is refused.

supplier-researcher

Read supplier investor pages

Fetches investor news from the suppliers on its list and flags changes for procurement.

Bringing it alltogether.

Connecting Apify to registered agents, models, and runtimes in Dome completes a governed agent application.
Dome

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

ApifyAgent service

Common questionsabout Apify.

Does Apify have a hosted MCP server?
Yes. Apify hosts one at mcp.apify.com, and Dome adds it by URL with an Apify API token.
Can I limit which Apify Actors an agent runs?
Yes. Rules read the actor argument of call-actor, so a named Actor runs and any other is refused.
Can I limit which websites an agent fetches through Apify?
Yes. Rules read the URL argument of Web Fetch, so a listed site is fetched and any other host is refused.
How do I choose which Apify tools an agent sees?
Set the tools parameter on the server URL. Apify serves only those, and Dome syncs that list into the catalog.

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

GitHub

The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity

Okta

Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client

Codex

Codex 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.

Every agent you run, under one system of control.