Generate music with MiniMax. Supports instrumental or vocal music. If lyrics and style are provided, generates a song. If no output path is provided, the audio file is saved to the default output directory (e.g. ./mmx_music).
AI agents invoke mmx_music_generate to trigger actions in Mmx. 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 music generation operation and writes the resulting audio file to the filesystem. It spans Write (file creation) and Execute (triggers external generative AI API call). The most severe applicable category is Execute, as it invokes an external service and produces side effects. Misuse could result in unwanted file creation or API quota consumption, giving it medium severity.
From the tool's definition Generate music with MiniMax... generates a song... the audio file is saved to the default output directory
Documented attack patterns abuse exactly the kind of access mmx_music_generate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mmx, and nothing reaches the server without passing your rules. This is the rule we recommend for mmx_music_generate:
{
"version": "1",
"default": "deny",
"tools": {
"mmx_music_generate": {
"limits": [
{
"counter": "mmx_music_generate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mmx_music_generate 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.
Generate music with MiniMax. Supports instrumental or vocal music. If lyrics and style are provided, generates a song. If no output path is provided, the audio file is saved to the default output directory (e.g. ./mmx_music). It is categorised as a Execute tool in the Mmx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mmx MCP server in PolicyLayer and add a rule for mmx_music_generate: 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 Mmx. Nothing to install.
mmx_music_generate 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 mmx_music_generate 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 mmx_music_generate. 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.
mmx_music_generate is provided by the Mmx MCP server (zth0828/mmx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mmx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Mmx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.