salesforce_update_record
Generic record update for any Salesforce object. For standard objects, prefer dedicated tools.
This record as markdown: /tools/freshdesk/salesforce-update-record.md
What salesforce_update_record does on Freshdesk
AI agents use salesforce_update_record 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_record is rated Medium
This tool modifies Salesforce records, which is a reversible write operation (existing records can be updated again to previous states). It is not destructive (does not permanently delete data), not financial (does not move money), and not execute (does not run arbitrary code—it updates specific record fields).
From the tool's definition Generic record update for any Salesforce object indicates modification of data in Salesforce. The term 'update' explicitly signals write operations that create or modify data reversibly.
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 Freshdesk, 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 Freshdesk, apply this rule, and every salesforce_update_record call is checked against it from then on.
Questions about salesforce_update_record
Generic record update for any Salesforce object. For standard objects, prefer dedicated tools. 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_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 Freshdesk. 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 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