Update one or more fields on an existing Salesforce Lead record. Pass the 18-character Lead ID and a fields object with any standard or custom field API names (e.g. Status, LeadSource, Title, Phone). Returns the updated record on success.
AI agents use sf_update_lead to create or update resources in Salesforce Marketing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Marketing environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Salesforce Lead ID |
fields | object | Yes | Fields to update |
Parameters from the server's own tool schema.
This tool modifies existing Lead records but does not delete or destroy data (thus not Destructive), does not execute arbitrary code (thus not Execute), and does not involve financial transactions (thus not Financial).
From the tool's definition Tool description states 'Update one or more fields on an existing Salesforce Lead record' — this is a modification operation that creates or changes data reversibly.
Attacks that exploit this kind of access
Update one or more fields on an existing Salesforce Lead record. Pass the 18-character Lead ID and a fields object with any standard or custom field API names (e.g. Status, LeadSource, Title, Phone). Returns the updated record on success. It is categorised as a Write tool in the Salesforce Marketing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sf_update_lead accepts 2 parameters: id, fields. Required: id, fields. The full parameter table on this page comes from the server's own tool schema.
Register the Salesforce Marketing MCP server in PolicyLayer and add a rule for sf_update_lead: 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 Marketing. Nothing to install.
sf_update_lead 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 sf_update_lead 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 sf_update_lead. 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.
sf_update_lead is provided by the Salesforce Marketing MCP server (salesforce-marketing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →