Vapi MCP server and Dome
Your agents place real phone calls, and you decide who they reach. Vapi's MCP server lets an agent place outbound calls through a Vapi assistant. Connect it to Dome once, and rules decide each call on the number it dials and the assistant that speaks. Every call an agent places lands in one audit trail.
Dome provides a governed gatewayfor Vapi.
US and Canadian numbers
Rules read customer.number on each create_call. Anything outside +1 is refused at the Gateway.
Assistants on a list
Rules read the assistant on every call, so only the assistants you've approved speak. Agents can't create or edit an assistant's script.
A ceiling on calls
Each agent gets two hundred tool calls a day, and the one after that is refused.
Vapi behind the Gatewayin four steps.
Add Vapi's server, sync it, deploy the assistant and number rules, then set each agent's ceiling.
Add the Vapi MCP server
Every agent shares one Vapi API key. Dome holds it and sends it as a Bearer token.
shelldome tools add --name vapi \ --url https://mcp.vapi.ai/mcp \ --auth-method api-key \ --credential-type shared \ --authorization "Bearer $VAPI_API_KEY" \ --gateway voice-gatewaySync the catalog
Vapi won't list its tools for a bad key, so sync with the real one.
shelldome tools catalog sync vapiApply the rules
The rules are scoped to renewal-caller. Simulate a call to a number outside +1, then deploy.
shelldome rules apply vapi-calls.cedar \ --agent renewal-caller --name vapi-callsCap the agent's calls
Two hundred a day for renewal-caller, counting every Vapi tool it calls.
shelldome quotas set --subject agent --agent renewal-caller \ --dimension tool --unit calls --limit 200 --window daily
Two assistants,North American numbers.
The permit opens Vapi to the agent. The first forbid closes the tools that write assistants. The second refuses any call unless a listed assistant dials a +1 number.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "vapi" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "vapi" && ["create_assistant", "update_assistant", "create_tool", "update_tool"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "vapi" && resource.tool_name == "create_call"}unless { resource has arguments && resource.arguments has assistantId && resource.arguments has customer && resource.arguments.customer has number && ["asst-renewal-reminder", "asst-appointment-confirm"].contains(resource.arguments.assistantId) && resource.arguments.customer.number like "+1*"};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Number
agent renewal-caller · scheduled
vapi/create_call(assistantId: "asst-renewal-reminder", customer: { number: "+14155550123" })
- Agentrenewal-caller is registered and active
- Assistantasst-renewal-reminder is on the list
- Rule+1 numbers are allowed
DecisionAllowed
Three agentson Vapi.
Two of them place calls, each through its own assistant, and one only reads what happened.
renewal-caller
Remind customers to renew
Calls customers in the US and Canada through the renewal assistant before a contract lapses, and is refused for any other number.
appointment-confirmer
Confirm appointments by phone
Calls each patient booked for the next day through the confirmation assistant and records the answer.
call-reviewer
Review yesterday's calls
Reads call records and flags any that ended early for a team lead, without placing calls itself.
Bringing it alltogether.
Connecting Vapi to registered agents, tools, and models in Dome completes a governed agent application.
Acting for
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
VapiAgent service
HubSpotMCP serverModels
Common questionsabout Vapi.
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
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.