update_record · Salesforce CLI MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_record does on Salesforce CLI MCP Server

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

WHY IT NEEDS A POLICY

Why update_record needs a policy

The tool modifies existing Salesforce records by updating specified fields. This is a Write operation—data is changed but not deleted, and changes are typically reversible through subsequent updates. Severity is high because updates to Salesforce records can affect business-critical data (customer records, opportunities, accounts, configurations) and may trigger downstream business logic or integrations.

From the tool's definition Tool name is 'update_record' and description states 'Update an existing record in a Salesforce org' and 'Updates specified fields on the record.' This is a modification operation that creates or alters data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_record Rate-limited

update_record 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": {
    "update_record": {
      "limits": [
        {
          "counter": "update_record_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 Salesforce CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about update_record

What does the update_record tool do? +

Update an existing record in a Salesforce org from a project using the SF CLI. Updates specified fields on the record. It is categorised as a Write tool in the Salesforce CLI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_record? +

Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for update_record: 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 Salesforce CLI MCP Server. Nothing to install.

What risk level is update_record? +

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

Can I rate-limit update_record? +

Yes. Add a rate_limit block to the update_record 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 update_record completely? +

Set action: deny in the PolicyLayer policy for update_record. 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 update_record? +

update_record is provided by the Salesforce CLI MCP Server MCP server (perrynet/salesforce-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.