list_custom_voices
List all custom voices you\
This record as markdown: /tools/freshdesk/list-custom-voices.md
What list_custom_voices does on Freshdesk
AI agents call list_custom_voices to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_custom_voices is rated Low
This tool retrieves or queries existing custom voices data without modifying, deleting, or executing any operations. It is a read-only operation that returns information, fitting the 'Read' category. The severity is low because listing voices poses minimal risk—there are no financial implications, data mutations, code execution, or destructive effects.
From the tool's definition Tool name is 'list_custom_voices' and description begins with 'List all custom voices you' — the verb 'List' indicates retrieval/querying with no side effects.
Attacks that exploit this kind of access
The rule that runs list_custom_voices 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 list_custom_voices, this is the rule to start with:
list_custom_voices is read-only, so it stays allowed. 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 list_custom_voices call is checked against it from then on.
Questions about list_custom_voices
List all custom voices you\. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_custom_voices: 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.
list_custom_voices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_custom_voices 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 list_custom_voices. 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.
list_custom_voices 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.
This server
Across the catalogue