Critical Risk →

delete_custom_voice

Delete a custom voice by ID. This is permanent and cannot be undone.

How to control delete_custom_voice ↓

What delete_custom_voice does on Freshdesk

AI agents call delete_custom_voice 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.

Critical Risk

Why delete_custom_voice needs a policy

This tool permanently and irreversibly deletes a custom voice resource. The description confirms the deletion cannot be reversed, meeting the definition of Destructive: irreversibly deletes or overwrites data, or actions that cannot be undone. The high severity reflects that an AI agent given this tool could accidentally destroy user-created voice configurations with no recovery path.

From the tool's definition Tool description explicitly states 'Delete a custom voice by ID. This is permanent and cannot be undone.' The words 'permanent' and 'cannot be undone' directly indicate irreversible data deletion.

Documented attack patterns abuse exactly the kind of access delete_custom_voice gives an agent:

How to control delete_custom_voice

PolicyLayer is an MCP gateway — it sits between your AI agents and Freshdesk, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_custom_voice:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_custom_voice"
  ]
}

delete_custom_voice disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Freshdesk — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_custom_voice

What does the delete_custom_voice tool do? +

Delete a custom voice by ID. This is permanent and cannot be undone. 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.

How do I enforce a policy on delete_custom_voice? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for delete_custom_voice: 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.

What risk level is delete_custom_voice? +

delete_custom_voice is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_custom_voice? +

Yes. Add a rate_limit block to the delete_custom_voice 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.

How do I block delete_custom_voice completely? +

Set action: deny in the PolicyLayer policy for delete_custom_voice. 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.

What MCP server provides delete_custom_voice? +

delete_custom_voice 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.

Enforce policy on every Freshdesk tool call.

Start from Freshdesk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

422 Freshdesk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.