generate_image_to_video
Generate a video from an image using Kling AI
This record as markdown: /tools/199-mcp-mcp-kling/generate-image-to-video.md
What generate_image_to_video does on MCP Kling
AI agents invoke generate_image_to_video to trigger actions in MCP Kling. 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.
Why generate_image_to_video is rated High
This tool triggers an external AI video generation operation using Kling AI's services, consuming computational resources and potentially API credits. It executes an external process whose effects depend on the input image and parameters. It's not purely destructive or financial, but it does trigger a real external operation beyond simple data writes.
From the tool's definition Generate a video from an image using Kling AI
Attacks that exploit this kind of access
The rule that runs generate_image_to_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Kling, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_image_to_video, this is the rule to start with:
generate_image_to_video stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Kling, apply this rule, and every generate_image_to_video call is checked against it from then on.
Questions about generate_image_to_video
Generate a video from an image using Kling AI. It is categorised as a Execute tool in the MCP Kling MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kling MCP server in PolicyLayer and add a rule for generate_image_to_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 MCP Kling. Nothing to install.
generate_image_to_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_image_to_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_image_to_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_image_to_video is provided by the MCP Kling MCP server (199-mcp/mcp-kling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Kling, and thousands of servers like it.
Across the catalogue