bulk_update_records · MCP Salesforce Connector MCP

WHAT IT DOES

What bulk_update_records does on MCP Salesforce Connector

AI agents use bulk_update_records to create or update resources in MCP Salesforce Connector — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Salesforce Connector environment.

WHY IT NEEDS A POLICY

Why bulk_update_records needs a policy

The tool creates or modifies data (updates) without irreversibly deleting it, placing it in the Write category. Severity is high because bulk operations affect multiple records simultaneously, creating significant blast radius if an LLM agent targets the wrong object type or applies unintended updates to many records in a production Salesforce environment.

From the tool's definition Tool name is 'bulk_update_records' and description states it 'Updates multiple records of a specified SObject type in bulk.' This is a write operation that modifies data reversibly.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_update_records Rate-limited

bulk_update_records stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bulk_update_records": {
      "limits": [
        {
          "counter": "bulk_update_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Salesforce Connector, so you can run agents against it safely.

FAQ

Questions about bulk_update_records

What does the bulk_update_records tool do? +

Updates multiple records of a specified SObject type in bulk. Each record must have an. It is categorised as a Write tool in the MCP Salesforce Connector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bulk_update_records? +

Register the MCP Salesforce Connector MCP server in PolicyLayer and add a rule for bulk_update_records: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Salesforce Connector. Nothing to install.

What risk level is bulk_update_records? +

bulk_update_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bulk_update_records? +

Yes. Add a rate_limit block to the bulk_update_records rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block bulk_update_records completely? +

Set action: deny in the PolicyLayer policy for bulk_update_records. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides bulk_update_records? +

bulk_update_records is provided by the MCP Salesforce Connector MCP server (smn2gnt/mcp-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.