Create a music generation task using AI models. Generate music from prompt and lyrics.\n\nNote: This tool calls MiniMax API and may incur costs. Use only when explicitly requested by the user.
AI agents use music_generation to commit financial operations through MiniMax MCP JS — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool explicitly warns it may incur costs by calling the MiniMax API, placing it in the Financial category as it commits financial obligations (API usage charges) each time it is invoked.
From the tool's definition "This tool calls MiniMax API and may incur costs. Use only when explicitly requested by the user."
Documented attack patterns abuse exactly the kind of access music_generation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MiniMax MCP JS, and nothing reaches the server without passing your rules. This is the rule we recommend for music_generation:
{
"version": "1",
"default": "deny",
"tools": {
"music_generation": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to music_generation is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a music generation task using AI models. Generate music from prompt and lyrics.\n\nNote: This tool calls MiniMax API and may incur costs. Use only when explicitly requested by the user. It is categorised as a Financial tool in the MiniMax MCP JS MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MiniMax MCP JS MCP server in PolicyLayer and add a rule for music_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 JS. Nothing to install.
music_generation is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the music_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 music_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.
music_generation is provided by the MiniMax MCP JS MCP server (minimax-ai/minimax-mcp-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MiniMax MCP JS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MiniMax MCP JS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.