Browse Workshops
Step 5

Test and Verify

⏱ 3 min

Overview

With the gateway instance created and both policies applied, you’ll use Postman’s native MCP client to connect to the governed endpoint and verify that tool calls reach Salesforce.

Step 1 — Find your Consumer Endpoint

  1. In MCP Servers, click Salesforce SObject All
  2. Click the Instances tab
  3. Click the Headless 360 instance
  4. Copy the Consumer Endpoint URL — it will look like: 
    https://<your-gateway-host>/headless-360-all

Step 2 — Connect Postman to the MCP Server

  1. Open Postman and create a new MCP Request
  2. In the Server URL field, paste your Consumer Endpoint URL
  3. Set Transport to Streamable HTTP
  4. Go to the Authorization tab:
    • Set Type to Basic Auth
    • Username: mcp-user
    • Password: mcp-pass
  5. Click Connect

Postman will establish an MCP session. Once connected, the session status will show Connected.

Step 3 — Discover available tools

Click the Tools tab in Postman. You should see the following tools exposed by the Salesforce SObject All server:

# Tool Description
1 getRelatedRecords Retrieves child records related to a parent record by traversing relationships
2 listRecentSobjectRecords Returns records recently viewed or modified by the user
3 soqlQuery Executes a SOQL query to retrieve Salesforce records
4 find Text search across multiple objects simultaneously
5 getUserInfo Returns current user’s identity, role, and preferences
6 getObjectSchema Returns Salesforce schema information optimised for LLM consumption
7 createSobjectRecord Creates a new record in any Salesforce object
8 updateSobjectRecord Updates fields on an existing record by ID
9 updateRelatedRecord Updates a child record by navigating from a parent through a relationship
10 deleteSobjectRecord Permanently deletes a record by ID
11 deleteRelatedRecord Deletes a child record by navigating a relationship from a parent

If you see the tools listed, the gateway is correctly proxying to Salesforce. ✓

Step 4 — Call the soqlQuery tool

  1. Click soqlQuery in the Tools list
  2. Fill in the input:
    • query: SELECT Id, Name FROM Account LIMIT 5
  3. Click Run Tool

The gateway will:

  1. Authenticate your Basic Auth credentials (inbound policy)
  2. Obtain a Salesforce OAuth2 token using Client Credentials (outbound policy)
  3. Forward the SOQL query to Salesforce
  4. Return the response

Expected result — a list of up to 5 Salesforce Account records.

Step 5 — Verify unauthenticated access is blocked

  1. In Postman, remove the Basic Auth credentials from the Authorization tab
  2. Click Connect again

You should receive a 401 Unauthorized error — the inbound Basic Authentication policy rejects the request before it reaches Salesforce. ✓

Troubleshooting

Symptom Resolution
401 Unauthorized with correct credentials Verify the Basic Authentication policy is Active in the Inbound policies tab
Postman connects but Tools tab is empty Wait 30 seconds for policy propagation and reconnect
502 Bad Gateway Check the Credential Injection policy is Active in the Outbound policies tab

What you’ve verified

  • Postman connects to the MCP Server with Basic Auth
  • Tools tab shows all 11 Salesforce SObject tools
  • soqlQuery returns Salesforce Account records
  • Unauthenticated request returns 401

Continue to Summary →