outreach_disconnect_account
Disconnect an Outreach account. Example: {
This record as markdown: /tools/freshdesk/outreach-disconnect-account.md
What outreach_disconnect_account does on Freshdesk
AI agents call outreach_disconnect_account to permanently remove resources in Freshdesk, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why outreach_disconnect_account is rated Critical
Disconnecting an account removes the established connection, which cannot be trivially undone and would disrupt all workflows, automations, and data flows dependent on that account integration. This is effectively irreversible without re-authentication and reconfiguration, placing it in the Destructive category with high severity given the blast radius of losing an account connection.
From the tool's definition 'Disconnect an Outreach account' — disconnecting an account is an irreversible action that removes the integration/authentication link between services
Attacks that exploit this kind of access
The rule that runs outreach_disconnect_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 outreach_disconnect_account, this is the rule to start with:
outreach_disconnect_account is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every outreach_disconnect_account call is checked against it from then on.
Questions about outreach_disconnect_account
Disconnect an Outreach account. Example: {. It is categorised as a Destructive tool in the Freshdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshdesk MCP server in PolicyLayer and add a rule for outreach_disconnect_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.
outreach_disconnect_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the outreach_disconnect_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 outreach_disconnect_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.
outreach_disconnect_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