remove_zendesk_account
Disconnect a Zendesk account. Removes the stored credentials for the specified subdomain. Use list_zendesk_accounts to see available subdomains.
This record as markdown: /tools/freshdesk/remove-zendesk-account.md
What remove_zendesk_account does on Freshdesk
AI agents call remove_zendesk_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 remove_zendesk_account is rated Critical
This tool irreversibly removes stored Zendesk account credentials/configuration. Once disconnected, the integration is broken and credentials are deleted, which cannot be undone without re-authenticating. This is a destructive operation with high blast radius as it would disable all Zendesk functionality for the affected subdomain.
From the tool's definition 'Removes the stored credentials for the specified subdomain' — permanently deletes/disconnects stored account credentials
Attacks that exploit this kind of access
The rule that runs remove_zendesk_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 remove_zendesk_account, this is the rule to start with:
remove_zendesk_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 remove_zendesk_account call is checked against it from then on.
Questions about remove_zendesk_account
Disconnect a Zendesk account. Removes the stored credentials for the specified subdomain. Use list_zendesk_accounts to see available subdomains. 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 remove_zendesk_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.
remove_zendesk_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 remove_zendesk_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 remove_zendesk_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.
remove_zendesk_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