Salesforce MCP server and Dome
Let agents read the CRM, and decide which records they change. Connect Salesforce's hosted sobject-all server to Dome once. Every call runs with the Salesforce login of the person the agent acts for, and rules decide each write on the object it names.
Dome provides a tool gatewayand authorization for Salesforce.
Decided on the object
The same tool is allowed on a Case and refused on an Opportunity, because rules read the sobject-name of every call.
Their login, their sharing rules
Each rep signs in to Salesforce once, on their first call. Field-level security and sharing still apply on top of Dome's rules.
Deletes refused
Rules name the tool. Record deletes and edits that climb to a parent record never reach Salesforce.
Salesforce behind the Gatewayin three steps.
Create an External Client App in Salesforce, add the server to Dome with its consumer key and secret, then apply the rules.
Add the Salesforce MCP server
The External Client App needs the mcp_api and refresh_token scopes. Credentials are per user, through OAuth.
shelldome tools add --name salesforce \ --url https://api.salesforce.com/platform/mcp/v1/platform/sobject-all \ --auth-method oauth --credential-type per-user \ --oauth-client-origin manual \ --oauth-client-id "$SF_CONSUMER_KEY" \ --oauth-client-secret "$SF_CONSUMER_SECRET" \ --oauth-authorize-url https://login.salesforce.com/services/oauth2/authorize \ --oauth-token-url https://login.salesforce.com/services/oauth2/token \ --oauth-default-scope mcp_api --oauth-default-scope refresh_token \ --gateway revenue-gatewaySync the catalog
Sync spends your own Salesforce credential, so sign in first. Until then it fails and agents get “tool not available in this gateway”.
shelldome tools catalog sync salesforceApply the rules
Scope them to one agent while you try them, and simulate before you deploy.
shelldome rules apply salesforce-args.cedar \ --agent case-triager --name salesforce-per-object
Casesand Tasks only.
The permit opens Salesforce to the agent. The first forbid refuses creates and updates on any object but Case and Task, and the second refuses deletes and parent-record edits.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "salesforce" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "salesforce" && ["createSobjectRecord", "updateSobjectRecord"].contains(resource.tool_name) && resource has arguments && resource.arguments has "sobject-name" && !["Case", "Task"].contains(resource.arguments["sobject-name"])};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "salesforce" && ["deleteSobjectRecord", "deleteRelatedRecord", "updateRelatedRecord"].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.
Object
agent case-triager · acting as t.mbeki
salesforce/updateSobjectRecord(sobject-name: "Case", id: "500Hs00001XyZaQ", body: { Priority: "High" })
- Agentcase-triager is registered and active
- Callert.mbeki verified through Microsoft Entra ID
- RuleUpdates to Cases are allowed
DecisionAllowed
Three agentson Salesforce.
These come from our template library, and each one reads broadly and writes narrowly.
case-triager
Triage support cases
Reads each new Case and the Account behind it, then sets priority and owner, with changes stopping at the Case.
pipeline-analyst
Answer pipeline questions
Answers questions about the pipeline from Opportunities and the contacts on them without writing anything.
renewal-tasker
Queue renewal follow-ups
Finds Accounts with a renewal in the next 90 days and creates a follow-up Task for each owner.
Bringing it alltogether.
Connecting Salesforce to registered agents, models, and identity in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
SalesforceMCP server
Models
Common questionsabout Salesforce.
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.
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
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
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.
MCP servers for AI agents: per-argument rules on every call
Put any remote MCP server behind the Tool Gateway. Agents reach it through one governed endpoint, and rules decide each call on its arguments.