Apollo.io MCP server and Dome
Let agents research prospects while keeping them out of your sequences. Apollo's MCP server gives agents people and company search, enrichment, contacts and sequences. A research agent needs the first two and none of the rest. Put Apollo behind Dome, and rules keep each agent to the lookups it needs while every call lands in one audit trail.
Dome provides a governed gatewayfor Apollo.
Lookups open, writes closed
Rules allow people search, company search and enrichment. Creating contacts and loading sequences stay refused for every research agent.
Each rep's own Apollo account
Each rep signs in to Apollo once through OAuth. Their agent calls Apollo with that rep's account, not a shared master key.
Personal emails decided per call
Rules read the arguments of every enrichment. A match that asks to reveal personal emails is refused.
Apollo behind the Gatewayin four steps.
Add Apollo's MCP server with per-user OAuth, sync its tools, apply the rules and cap the calls. Agents reach Apollo through the Gateway's single MCP endpoint.
Add the Apollo MCP server
Dome registers itself with Apollo's OAuth server. Each rep signs in to Apollo once, and Dome stores their token.
shelldome tools add --name apollo \ --url https://mcp.apollo.io/mcp \ --auth-method oauth \ --credential-type per-user \ --oauth-client-origin dcr \ --oauth-authorize-url https://mcp.apollo.io/mcp/oauth_metadata/redirect_to_authorize \ --oauth-token-url https://mcp.apollo.io/api/v1/oauth/token \ --oauth-revoke-url https://mcp.apollo.io/api/v1/oauth/revoke \ --oauth-registration-url https://mcp.apollo.io/api/v1/oauth/applications/register_oauth_client \ --gateway prod-gatewaySync the catalog
Sync runs with your own Apollo sign-in, so connect your account first. Until it runs, agents get “tool not available in this gateway”.
shelldome tools catalog sync apolloApply the rules
Scope them to one agent while you try them, and simulate before you deploy.
shelldome rules apply apollo-lookups.cedar --agent lead-enricher --name apollo-lookupsCap the calls
The quota counts every tool call the agent makes. Past the limit, calls are refused until the window resets.
shelldome quotas set --subject agent --agent lead-enricher \ --dimension tool --unit calls --limit 200 --window daily
Search and enrich,never write.
The permit opens four lookup tools. One forbid closes every other Apollo tool, contacts and sequences included. The other refuses a people match that asks for personal emails.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "apollo" && ["apollo_mixed_people_api_search", "apollo_mixed_companies_search", "apollo_organizations_enrich", "apollo_people_match"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "apollo" && !["apollo_mixed_people_api_search", "apollo_mixed_companies_search", "apollo_organizations_enrich", "apollo_people_match"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "apollo" && resource.tool_name == "apollo_people_match" && resource has arguments && resource.arguments has reveal_personal_emails && resource.arguments.reveal_personal_emails == true};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Request
agent lead-enricher · acting as j.okafor
apollo/apollo_people_match(first_name: "Dana", last_name: "Reyes", domain: "northwind-supply.com")
- Agentlead-enricher is registered and active
- Callerj.okafor verified through Okta
- RulePeople match without personal emails is allowed
DecisionAllowed
Three agentson Apollo.
Each one looks people and companies up. None of them creates a contact or loads a sequence.
account-researcher
Map the buying group
Finds the decision makers at a target account by title and seniority, and writes a short map for the rep.
lead-enricher
Enrich inbound leads
Matches each inbound lead to a person and a company, and is refused if it asks for personal emails.
meeting-prep
Prepare for a first call
Looks up the company and the people on the invite before a first meeting, and drafts a one-page brief.
Bringing it alltogether.
Connecting Apollo to registered agents, CRM tools, and identity in Dome completes a governed agent application.
Acting for
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
ApolloAgent service
HubSpotMCP serverModels
Common questionsabout Apollo.
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
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.