Salesforce MCP server and Dome

1. 01

   Add the Salesforce MCP server

   The External Client App needs the mcp_api and refresh_token scopes. Credentials are per user, through OAuth.

   $ dome 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-gateway

2. 02

   Sync 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”.

   $ dome tools catalog sync salesforce

3. 03

   Apply the rules

   Scope them to one agent while you try them. Simulate before you deploy.

   $ dome rules apply salesforce-args.cedar \
     --agent case-triager --name salesforce-per-object

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Salesforce itself, see Salesforce's documentation.

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)
};