salesforce_create_contact
Create a contact. Required: last_name. Optional: first_name, email, phone, title, related_account_id, fields.
This record as markdown: /tools/freshdesk/salesforce-create-contact.md
What salesforce_create_contact does on Freshdesk
AI agents use salesforce_create_contact 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_create_contact is rated Medium
This tool creates new contact records in Salesforce, which is a reversible data modification operation. It does not delete, execute arbitrary commands, or move money. The severity is medium because creating contacts could lead to data pollution, duplicate records, or unauthorized contact creation in a CRM system if misused by an AI agent, but the impact is limited to new record creation and reversible through…
From the tool's definition Tool description states "Create a contact" with optional and required parameters for contact details (last_name, first_name, email, phone, title, etc.). The verb "Create" indicates data creation.
Attacks that exploit this kind of access
The rule that runs salesforce_create_contact 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_create_contact, this is the rule to start with:
salesforce_create_contact 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_create_contact call is checked against it from then on.
Questions about salesforce_create_contact
Create a contact. Required: last_name. Optional: first_name, email, phone, title, related_account_id, 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_create_contact: 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_create_contact 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_create_contact 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_create_contact. 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_create_contact 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