Create a lipsync video by synchronizing audio with video
AI agents use create_lipsync to create or update resources in Tavus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tavus MCP Server environment.
This tool creates new video content (lipsync synchronization) which is reversible data creation. It modifies or generates media artifacts but does not execute arbitrary code, delete data, or move money. The 'create' operation and presence of corresponding 'delete_lipsync' on the same server confirm this is a Write operation.
From the tool's definition Tool name is 'create_lipsync' and description states 'Create a lipsync video by synchronizing audio with video', indicating creation of new media content.
Attacks that exploit this kind of access
Create a lipsync video by synchronizing audio with video. It is categorised as a Write tool in the Tavus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tavus 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 Tavus 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 Tavus MCP Server MCP server (rakeshdavid/tavus-mcp). 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 →