列出可用的语音音色
AI agents call list_available_voices to retrieve information from Auto Video Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates a list of available voices for the text-to-speech synthesis feature. It is a read-only operation with no side effects, no data modification, no code execution, and no destructive or financial implications. The blast radius if misused is minimal—an agent could only discover what voices exist, which is informational metadata.
From the tool's definition Tool name 'list_available_voices' and description '列出可用的语音音色' (list available voice tones/voices) indicates a query operation that retrieves information about available voice options without modifying or executing operations.
Attacks that exploit this kind of access
列出可用的语音音色. It is categorised as a Read tool in the Auto Video Generator MCP Server, which means it retrieves data without modifying state.
Register the Auto Video Generator MCP server in PolicyLayer and add a rule for list_available_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 Auto Video Generator. Nothing to install.
list_available_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_available_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_available_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_available_voices is provided by the Auto Video Generator MCP server (zgmurder/auto_video_generator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →