// SCAN REPORT

MCP Salesforce Connector

14 tools. 10 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 27 Jun 2026

10 can modify or destroy data

4 read-only

14 tools total

Community server · catalogue entry verified 27/06/2026

How to control MCP Salesforce Connector ↓

TOOL MAP

What MCP Salesforce Connector exposes to your agents

Read (4) Write / Execute (8) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Salesforce Connector tools

Destructive · Critical bulk_delete_records This tool permanently removes data from Salesforce without possibility of reversal (unless backup/recovery is available outside the tool). Destructive · High delete_record The delete_record tool permanently removes records from Salesforce and cannot be undone. Execute · High apex_execute This tool executes arbitrary Apex code on Salesforce servers. Execute · High restful The tool's effects are entirely argument-dependent: it could retrieve data (Read), modify records (Write), delete records (Destructive), execute Apex code (Execute), or trigger financial operations (Financial) based on w

10 of MCP Salesforce Connector's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Salesforce Connector

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Salesforce Connector, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "bulk_delete_records": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "bulk_create_records": {
    "limits": [
      {
        "counter": "bulk_create_records_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "run_sosl_search": {
    "limits": [
      {
        "counter": "run_sosl_search_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Salesforce Connector — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP SALESFORCE CONNECTOR →

Instant setup, no code required.

FULL CATALOGUE

All 14 MCP Salesforce Connector tools

DESTRUCTIVE 2 tools

Destructive bulk_delete_records Deletes multiple records of a specified SObject type in bulk, given their IDs. Destructive delete_record Deletes a record

EXECUTE 4 tools

Execute apex_execute Executes an Apex REST request Execute restful Makes a direct REST API call to Salesforce Execute run_soql_query run_soql_query Execute tooling_execute Executes a Tooling API request

WRITE 4 tools

Write bulk_create_records Creates multiple records of a specified SObject type in bulk. Write bulk_update_records Updates multiple records of a specified SObject type in bulk. Each record must have an Write create_record Creates a new record Write update_record Updates an existing record

READ 4 tools

Read run_sosl_search run_sosl_search Read get_object_fields get_object_fields Read get_record get_record Read list_sobjects Retrieves a list of all available Salesforce SObjects (standard and custom).

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MCP Salesforce Connector

Can an AI agent delete data through the MCP Salesforce Connector MCP server? +

Yes. The MCP Salesforce Connector server exposes 2 destructive tools including bulk_delete_records, delete_record. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MCP Salesforce Connector? +

The MCP Salesforce Connector server has 4 write tools including bulk_create_records, bulk_update_records, create_record. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MCP Salesforce Connector.

How many tools does the MCP Salesforce Connector MCP server expose? +

14 tools across 4 categories: Destructive, Execute, Read, Write. 4 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on MCP Salesforce Connector? +

Register the MCP Salesforce Connector MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Salesforce Connector tool call.

Deterministic rules across all 14 MCP Salesforce Connector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP SALESFORCE CONNECTOR →

Instant setup, no code required.

14 MCP Salesforce Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.