Generate video with MiniMax from a text prompt. If no output path is provided, the video is saved to the default output directory (e.g. ./mmx_video) and its file path is returned.
AI agents use mmx_video_generate to create or update resources in Mmx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mmx environment.
This tool generates and writes a video file to the filesystem based on a text prompt. It creates new data (a video file) and saves it to disk, which is a Write operation. It does not delete data, execute arbitrary code, or involve financial transactions. Severity is medium because it consumes API quota and writes files to the filesystem, but the blast radius is limited.
From the tool's definition Generate video with MiniMax from a text prompt... the video is saved to the default output directory... and its file path is returned.
Documented attack patterns abuse exactly the kind of access mmx_video_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_video_generate:
{
"version": "1",
"default": "deny",
"tools": {
"mmx_video_generate": {
"limits": [
{
"counter": "mmx_video_generate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mmx_video_generate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate video with MiniMax from a text prompt. If no output path is provided, the video is saved to the default output directory (e.g. ./mmx_video) and its file path is returned. It is categorised as a Write tool in the Mmx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mmx MCP server in PolicyLayer and add a rule for mmx_video_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_video_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mmx_video_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_video_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_video_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.