create_lipsync
Create a lip-sync video by synchronizing mouth movements with audio. Supports both text-to-speech (TTS) with various voice options or custom audio upload. The original video must contain a clear, steady human face with visible mouth. Works with real, 3D, or 2D human characters (not animals). Vide...
This record as markdown: /tools/199-mcp-mcp-kling/create-lipsync.md
What create_lipsync does on MCP Kling
AI agents invoke create_lipsync 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 create_lipsync is rated High
This tool triggers an external AI video generation operation — it processes an existing video and audio to produce a new lip-synced video. This is an Execute action: it invokes an external computational service whose output depends on the inputs (video, audio/TTS). It is not purely a Write (no simple data record is created) and not Destructive or Financial.
From the tool's definition Create a lip-sync video by synchronizing mouth movements with audio. Supports both text-to-speech (TTS) with various voice options or custom audio upload.
Attacks that exploit this kind of access
The rule that runs create_lipsync 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 create_lipsync, this is the rule to start with:
create_lipsync 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 create_lipsync call is checked against it from then on.
Questions about create_lipsync
Create a lip-sync video by synchronizing mouth movements with audio. Supports both text-to-speech (TTS) with various voice options or custom audio upload. The original video must contain a clear, steady human face with visible mouth. Works with real, 3D, or 2D human characters (not animals). Video length limited to 10 seconds. 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 create_lipsync: 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.
create_lipsync 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 create_lipsync 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 create_lipsync. 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.
create_lipsync 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