salesforce_update_lead
Update a lead. Required: lead_id. Updatable: first_name, last_name, company, email, phone, title, status, fields.
This record as markdown: /tools/freshdesk/salesforce-update-lead.md
What salesforce_update_lead does on Freshdesk
AI agents use salesforce_update_lead to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why salesforce_update_lead is rated Medium
The tool creates or modifies data (lead records) in Salesforce reversibly without permanently deleting or destroying records. It does not execute arbitrary code, trigger financial transactions, or irreversibly delete data. The severity is high because misuse could corrupt critical business lead data affecting sales operations, but changes can be reverted.
From the tool's definition Tool name and description explicitly state 'Update a lead' with updatable fields including first_name, last_name, company, email, phone, title, status, and custom fields. This modifies existing CRM data reversibly.
Attacks that exploit this kind of access
The rule that runs salesforce_update_lead safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For salesforce_update_lead, this is the rule to start with:
salesforce_update_lead 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 Freshdesk, apply this rule, and every salesforce_update_lead call is checked against it from then on.
Questions about salesforce_update_lead
Update a lead. Required: lead_id. Updatable: first_name, last_name, company, email, phone, title, status, fields. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for salesforce_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 Freshdesk. Nothing to install.
salesforce_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 salesforce_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 salesforce_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.
salesforce_update_lead is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue