generate_video
AI agents invoke generate_video to trigger actions in MiniMax MCP Server. 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.
Based on the server context, this tool likely triggers an external video generation operation via the MiniMax API. The sibling tool 'query_video_generation' suggests video generation is an asynchronous external operation, making this an Execute-category action. Severity is high due to potential resource consumption and API costs, though confidence is reduced due to empty description.
From the tool's definition Tool name 'generate_video' on a server described as enabling 'creating videos'; description is empty and uninformative.
Attacks that exploit this kind of access
generate_video. It is categorised as a Execute tool in the MiniMax MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MiniMax MCP Server MCP server in PolicyLayer and add a rule for generate_video: 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 Server. Nothing to install.
generate_video 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 generate_video 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 generate_video. 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.
generate_video is provided by the MiniMax MCP Server MCP server (minimax-ai/minimax-mcp). 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 →