Generate a video using Luma
AI agents invoke piapi_generate_video_luma to trigger actions in MCP TS Toolkit. 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.
This tool executes an external API call to generate video content using the Luma AI model through PiAPI.ai. It triggers an external operation whose effects depend on the input arguments (prompt, settings, etc.). It is not purely a read operation, and while it may incur costs, its primary classification is Execute as it runs an external generative AI process.
From the tool's definition "Generate a video using Luma" — triggers an external AI video generation operation via PiAPI.ai integration
Attacks that exploit this kind of access
Generate a video using Luma. It is categorised as a Execute tool in the MCP TS Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP TS Toolkit MCP server in PolicyLayer and add a rule for piapi_generate_video_luma: 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 TS Toolkit. Nothing to install.
piapi_generate_video_luma 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 piapi_generate_video_luma 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 piapi_generate_video_luma. 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.
piapi_generate_video_luma is provided by the MCP TS Toolkit MCP server (thomas92fr/mcp-ts-toolskit). 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 →