Query the status of a video generation task.
AI agents call query_video_generation to retrieve information from MiniMax MCP JS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing video generation task's status. It performs no side effects, creates no new tasks, modifies no data, and executes no operations. Status queries are non-destructive read operations that fall squarely into the Read category with low severity since they only expose task metadata.
From the tool's definition Tool name contains 'query' and description states 'Query the status of a video generation task', indicating a retrieval operation that checks task status without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access query_video_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 query_video_generation:
{
"version": "1",
"default": "deny",
"tools": {
"query_video_generation": {}
}
}query_video_generation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query the status of a video generation task. It is categorised as a Read tool in the MiniMax MCP JS MCP Server, which means it retrieves data without modifying state.
Register the MiniMax MCP JS MCP server in PolicyLayer and add a rule for query_video_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.
query_video_generation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the query_video_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 query_video_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.
query_video_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.