Announcing Dome Managed Agents.

Try it now

ElevenLabs MCP and Dome

Voice agents talk to your customers, and you decide what they look up. ElevenLabs Agents reach outside tools through custom MCP servers, added by URL and secret token. Point one at a Dome Gateway, and the voice agent reaches your tools as a registered agent with its own key. Rules decide each call it makes mid-conversation, and audit records every one.

Dome provides a governed gatewayfor ElevenLabs Agents.

A key per voice agent

Each ElevenLabs agent connects with its own Dome key as the secret token. Revoke one key and only that agent loses access.

Reads open, writes closed

Rules decide every tool call the voice agent makes mid-conversation. It looks up a caller's record and can't change it.

Every lookup audited

Each tool call lands in audit under the voice agent's name. You see what it read during every call.

ElevenLabs Agents on a Gatewayin four steps.

Register the voice agent, give it a key, apply the rules, and add the Gateway to ElevenLabs as a custom MCP server. Your tools stay behind the Gateway the whole time.
  1. Register the voice agent

    Name the tools it may call and the Gateway it reaches.

    shell
    dome agents register --name support-voice \  --tool hubspot/search_crm_objects \  --tool hubspot/get_crm_objects \  --tool hubspot/search_owners \  --gateway support-gateway
  2. Create its key

    The response carries the key and the Gateway's MCP URL. Store the key in ElevenLabs and nowhere else.

    shell
    dome agents create-key support-voice --name elevenlabs --gateway support-gateway
  3. Apply the rules

    The Gateway grant opens every tool on the Gateway, and the forbid narrows it to three. Simulate before you deploy.

    shell
    dome rules apply support-voice.cedar \  --agent support-voice --name support-voice
  4. Add the Gateway to ElevenLabs

    In ElevenLabs, open the MCP server integrations and add a custom MCP server. Paste the MCP URL, set the secret token to Bearer and the key, then attach the server to your agent.

Three HubSpot reads,nothing else.

The permit opens HubSpot to the voice agent. The forbid refuses every tool call that isn't one of three reads, so writes and every other tool on the Gateway stay closed.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "hubspot" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)unless {  resource.connection_name == "hubspot" &&  ["search_crm_objects", "get_crm_objects", "search_owners"].contains(resource.tool_name)};

One call,two outcomes.

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

Call

agent support-voice · scheduled
hubspot/search_crm_objects(the contact whose phone is +1 415 555 0123)
  1. Agentsupport-voice is registered and active
  2. KeyThe ElevenLabs key belongs to support-voice
  3. Rulesearch_crm_objects is one of three reads
DecisionAllowed

Three agentsaround ElevenLabs.

Two ElevenLabs voice agents, each with its own key and rules. One of your own agents works from what they recorded.

support-voice

Answer support calls

Looks up the caller's contact record and its owner while it talks, reading HubSpot without changing anything.

billing-voice

Answer billing questions

Reads a caller's invoices in a Stripe sandbox while it talks. Its own key and rules keep it out of HubSpot.

call-summarizer

Log what each call covered

Reads the day's support records and drafts follow-ups for the team lead without ever speaking to a caller.

Bringing it alltogether.

Connecting ElevenLabs Agents to registered tools, models, and identity in Dome completes a governed agent application.
Dome

Acting for

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

ElevenLabs AgentsAgent service
HubSpotMCP serverStripeMCP server

Common questionsabout ElevenLabs Agents.

Can ElevenLabs Agents connect to a remote MCP server?
Yes. ElevenLabs adds custom MCP servers by URL, with an optional secret token sent as the Authorization header.
How do I limit which tools an ElevenLabs voice agent can call?
Register it in Dome and point it at a Gateway. Rules decide each tool call, so it reaches only the tools you list.
Does each ElevenLabs agent need its own Dome key?
It should. Each key belongs to one registered agent, so rules and audit tell your voice agents apart.
Does Dome place ElevenLabs phone calls?
No. ElevenLabs places the call, and Dome decides the tool calls its agent makes during it.

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

LangGraph

LangGraph agents with their model calls 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.