salesforce_update_record
A write tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/salesforce-update-record.md
What salesforce_update_record does on Integrations MCP
AI agents use salesforce_update_record to create or update resources in Integrations MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Why salesforce_update_record is rated Medium
The tool modifies existing records in Salesforce, a major SaaS platform, which is a Write operation. Although the description is empty, the naming pattern and context from sibling tools strongly indicate this performs record updates.
From the tool's definition Tool name is 'salesforce_update_record' indicating modification of data in Salesforce. Sibling tools include 'airtable_update_record' and 'airtable_create_record' which are clearly Write operations. The 'update' verb confirms reversible data modification.
Attacks that exploit this kind of access
The rule that runs salesforce_update_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For salesforce_update_record, this is the rule to start with:
salesforce_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every salesforce_update_record call is checked against it from then on.
Questions about salesforce_update_record
salesforce_update_record is a write tool on the Integrations MCP server. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for salesforce_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 Integrations MCP. Nothing to install.
salesforce_update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the salesforce_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.
Set action: deny in the PolicyLayer policy for salesforce_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.
salesforce_update_record is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue