salesforce_connect_account
Connect a Salesforce account via OAuth. Takes no parameters — call with {}. Initiates OAuth flow — in standalone mode, opens a browser URL for Salesforce sign-in. In bridge mode, delegates to the host app. WHEN TO USE: - No Salesforce account is connected - Authentication errors from other tools ...
This record as markdown: /tools/freshdesk/salesforce-connect-account.md
What salesforce_connect_account does on Freshdesk
AI agents invoke salesforce_connect_account to trigger actions in Freshdesk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why salesforce_connect_account is rated High
This tool triggers an external operation (OAuth authentication flow) that opens a browser URL or delegates to a host app. It doesn't merely read or write data — it executes an authentication/authorization workflow with side effects in an external system. Severity is medium as misuse could result in unauthorized account linkage or phishing-style redirects.
From the tool's definition Initiates OAuth flow — in standalone mode, opens a browser URL for Salesforce sign-in. In bridge mode, delegates to the host app.
Attacks that exploit this kind of access
The rule that runs salesforce_connect_account 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_connect_account, this is the rule to start with:
salesforce_connect_account stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_connect_account call is checked against it from then on.
Questions about salesforce_connect_account
Connect a Salesforce account via OAuth. Takes no parameters — call with {}. Initiates OAuth flow — in standalone mode, opens a browser URL for Salesforce sign-in. In bridge mode, delegates to the host app. WHEN TO USE: - No Salesforce account is connected - Authentication errors from other tools - User asks to connect Salesforce After connecting, verify with salesforce_list_connected_accounts. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk MCP server in PolicyLayer and add a rule for salesforce_connect_account: 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_connect_account is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the salesforce_connect_account 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_connect_account. 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_connect_account 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.
Across the catalogue