Convert text to speech asynchronously. RECOMMENDED: Submit multiple tasks in batch to saturate rate limits, then call task_barrier once to wait for all completions. Returns task ID only - actual files available after task_barrier.
AI agents invoke submit_speech_generation to trigger actions in Minimax MCP Tools. 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 API operation (Minimax TTS) that generates audio files asynchronously. It executes an external process and produces output files, classifying it as Execute. Severity is medium because misuse could generate unwanted audio files, consume API credits, or saturate rate limits, but it doesn't directly move money or irreversibly destroy data.
From the tool's definition Convert text to speech asynchronously... Submit multiple tasks in batch to saturate rate limits... Returns task ID only - actual files available after task_barrier
Documented attack patterns abuse exactly the kind of access submit_speech_generation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Minimax MCP Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_speech_generation:
{
"version": "1",
"default": "deny",
"tools": {
"submit_speech_generation": {
"limits": [
{
"counter": "submit_speech_generation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}submit_speech_generation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Convert text to speech asynchronously. RECOMMENDED: Submit multiple tasks in batch to saturate rate limits, then call task_barrier once to wait for all completions. Returns task ID only - actual files available after task_barrier. It is categorised as a Execute tool in the Minimax MCP Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Minimax MCP Tools MCP server in PolicyLayer and add a rule for submit_speech_generation: 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 Minimax MCP Tools. Nothing to install.
submit_speech_generation 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 submit_speech_generation 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 submit_speech_generation. 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.
submit_speech_generation is provided by the Minimax MCP Tools MCP server (psycharch/minimax-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Minimax MCP Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Minimax MCP Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.