update_lead
AI agents use update_lead to create or update resources in Salesforce MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce MCP Server environment.
This tool creates or modifies data reversibly within Salesforce's lead management system. It is not destructive (no deletion), not execute (no code execution), and not financial (no money movement). The severity is medium because misuse could corrupt important sales pipeline data affecting business processes, but the change is reversible through subsequent updates.
From the tool's definition Tool name is 'update_lead' which modifies an existing lead record in Salesforce. The description is empty, but the name and context (sibling tools include create_lead, delete_lead, create_contact, etc.) clearly indicate this is a data modification operation.
Attacks that exploit this kind of access
update_lead. It is categorised as a Write tool in the Salesforce MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.
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 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 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.
update_lead is provided by the Salesforce MCP Server MCP server (obot-platform/salesforce-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 →