AI agents invoke create_speech to trigger actions in Litellm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external AI/API operation (text-to-speech generation) that consumes compute resources and potentially incurs costs. It doesn't merely read data, but executes an audio generation process via an external service. It's not purely destructive or financial, but it does trigger an external operation whose effects (audio generation, API usage, potential cost) depend on input arguments.
From the tool's definition Generate speech audio from text using LiteLLM (/audio/speech)
Attacks that exploit this kind of access
Generate speech audio from text using LiteLLM (/audio/speech). It is categorised as a Execute tool in the Litellm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Litellm MCP server in PolicyLayer and add a rule for create_speech: 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 Litellm. Nothing to install.
create_speech is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_speech 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 create_speech. 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.
create_speech is provided by the Litellm MCP server (litellm-mcp-server). 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 →