Create a lipsync video from audio + EITHER a video or a still image (an image drives sync-3 image-to-video).
AI agents use create-lipsync to create or update resources in Sync MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sync MCP Server environment.
This tool creates a new lipsync video asset by combining audio with video or image input. It generates new content (reversible in the sense that the source assets are not destroyed), making it a Write operation. Severity is medium because misuse could generate unauthorized or unwanted video content consuming API credits, but it doesn't delete data or move money.
From the tool's definition Create a lipsync video from audio + EITHER a video or a still image
Attacks that exploit this kind of access
Create a lipsync video from audio + EITHER a video or a still image (an image drives sync-3 image-to-video). It is categorised as a Write tool in the Sync MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sync MCP Server 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 Sync MCP Server. Nothing to install.
create-lipsync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Sync MCP Server MCP server (synchronicity-labs/mcp-server). 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 →