Announcing Dome Managed Agents.

Try it now

Exa and Dome

Your agents' searches say what you're working on, and rules can check them before they leave. Exa's hosted MCP server gives agents search, page fetches and an agent_run tool besides. Research agents search a lot, and every query carries context. Put Exa behind Dome, and each agent gets two tools, a daily call budget and a rule on what it may search for.

Dome provides a governed gatewayfor Exa.

Every spelling of the codename

Cedar's like is case-sensitive. List Halcyon and HALCYON, and a query or objective with either is refused before Exa sees it.

Two tools, not three

Search and fetch stay open. A forbid closes agent_run and every other Exa tool.

A budget per agent

A quota counts each Exa call an agent makes. Past the daily limit, the next one is refused.

Exa behind the Gatewayin five steps.

Add Exa's server, sync it, guard outbound arguments, deploy the rules and set each agent's budget.
  1. Add the Exa MCP server

    Exa reads its API key from the x-api-key header. Dome stores the key and sends it on every call.

    shell
    dome tools add --name exa \  --url https://mcp.exa.ai/mcp \  --auth-method api-key \  --credential-type shared \  --authorization "Bearer $EXA_API_KEY" \  --secret-value EXA_API_KEY=$EXA_API_KEY \  --header-secret x-api-key=EXA_API_KEY \  --gateway prod-gateway
  2. Sync the catalog

    Sync lists web_search_exa, web_fetch_exa and agent_run. Agents see none of them until it runs.

    shell
    dome tools catalog sync exa
  3. Block personal data in arguments

    A JSON filter on the request direction scans every argument. A match blocks the call before it reaches Exa.

    shell
    cat > query-leak.json <<'EOF'{"json":{"components":[{"fieldActions":[{  "matcher":{"contentMatchers":[{"ssn":{}},{"creditCard":{"requireLuhn":true}},{"email":{}}]},  "action":"FILTER_ACTION_BLOCK"}]}]}}EOFdome guards filters create query-leak --config-from query-leak.jsondome tools guards filters set exa --direction request --filters query-leak
  4. Apply the rules

    The rule is scoped to deal-scout. Simulate a query with each spelling of the codename, then deploy.

    shell
    dome rules apply exa-queries.cedar --agent deal-scout --name exa-queries
  5. Cap the calls

    The quota counts every tool call the agent makes. Past the limit, calls are refused until the window resets.

    shell
    dome quotas set --subject agent --agent deal-scout \  --dimension tool --unit calls --limit 500 --window daily

Search and fetch,never the codename.

The permit opens search and fetch. One forbid closes every other Exa tool, and the other refuses any query or objective that names Project Halcyon. Cedar's like is case-sensitive, so list each spelling you need.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "exa" &&  ["web_search_exa", "web_fetch_exa"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "exa" &&  !["web_search_exa", "web_fetch_exa"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "exa" &&  resource has arguments &&  ((resource.arguments has query && resource.arguments.query like "*Halcyon*") ||   (resource.arguments has objective && resource.arguments.objective like "*Halcyon*"))};

One call,two outcomes.

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

Query

agent deal-scout · acting as m.chen
exa/web_search_exa(query: "industrial sensor startups Series B 2026", objective: "Map the market")
  1. Agentdeal-scout is registered and active
  2. Callerm.chen verified through Okta
  3. RuleThe query names no internal project
DecisionAllowed

Three agentson Exa.

Each one searches the open web. None of them sends an internal name or a customer's details to do it.

market-researcher

Map a market

Searches for companies in a category and reads their sites, with a daily quota capping its calls.

regulatory-tracker

Track new rules

Searches regulators' sites each morning and fetches anything new for the compliance team.

deal-scout

Scout acquisition targets

Runs targeted searches against a deal thesis. Any listed spelling of the deal's codename is refused.

Bringing it alltogether.

Connecting Exa to registered agents, models, and identity in Dome completes a governed agent application.
Dome

Acting for

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

ExaAgent service

Common questionsabout Exa.

Does Exa have an MCP server?
Yes. Exa hosts one at mcp.exa.ai/mcp, and Dome adds it by URL with the API key in the x-api-key header.
Does a codename rule catch every spelling?
Only the spellings you list. Cedar's like is case-sensitive, so the rule names each one, and a query or objective with any of them is refused.
Can Dome keep customer details out of Exa?
Yes. A guard on the request direction blocks a call whose arguments carry an email address, a card number or a Social Security number.
Can I limit how many Exa searches an agent runs?
Yes. A quota on the agent with --dimension tool --unit calls caps its tool calls each day or month.

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

Microsoft Entra ID

Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
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.

Every agent you run, under one system of control.