Query the status and result of a video generation task. Use this to check if a generation is complete and retrieve the resulting video URLs, thumbnails, and other metadata. Use this when: - You want to check if a generation has completed - You need to retrieve video URLs from a previous generatio...
Part of the Mcp Luma server.
Free to start. No card required.
AI agents call luma_get_task to retrieve information from Mcp Luma without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though luma_get_task only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"luma_get_task": {}
}
}See the full Mcp Luma policy for all 8 tools.
These attack patterns abuse exactly the kind of access luma_get_task gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Query the status and result of a video generation task. Use this to check if a generation is complete and retrieve the resulting video URLs, thumbnails, and other metadata. Use this when: - You want to check if a generation has completed - You need to retrieve video URLs from a previous generation - You want to get the full details of a generated video Task states: - 'pending': Generation is still in progress - 'completed': Generation finished successfully - 'failed': Generation failed (check error message) Returns: Task status and generated video information including URLs, dimensions, and thumbnail.. It is categorised as a Read tool in the Mcp Luma MCP Server, which means it retrieves data without modifying state.
Register the Mcp Luma MCP server in PolicyLayer and add a rule for luma_get_task: 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 Mcp Luma. Nothing to install.
luma_get_task 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 luma_get_task 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 luma_get_task. 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.
luma_get_task is provided by the Mcp Luma MCP server (acedatacloud-mcp/mcp-luma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mcp Luma tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.