remove_freshdesk_account
Disconnect a Freshdesk account. Removes stored credentials for the specified domain.
This record as markdown: /tools/freshdesk/remove-freshdesk-account.md
What remove_freshdesk_account does on Freshdesk
AI agents call remove_freshdesk_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_freshdesk_account is rated Critical
The tool permanently deletes stored credentials, which cannot be undone. Once removed, access to the Freshdesk account is lost and credentials must be re-entered. This is destructive data loss, even though it doesn't delete customer or ticket data directly. The high severity reflects that an AI agent removing credentials without authorization would break Freshdesk integration and require manual recovery.
From the tool's definition Tool description states 'Removes stored credentials for the specified domain' — this is irreversible deletion of authentication data.
Attacks that exploit this kind of access
The rule that runs remove_freshdesk_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_freshdesk_account, this is the rule to start with:
remove_freshdesk_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_freshdesk_account call is checked against it from then on.
Questions about remove_freshdesk_account
Disconnect a Freshdesk account. Removes stored credentials for the specified domain. 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_freshdesk_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_freshdesk_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_freshdesk_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_freshdesk_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_freshdesk_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