gen_avatar_video
Async talking-avatar video via HeyGen (text→avatar). BYOK ONLY; requires your own HeyGen avatar_id (+ voice_id). Returns {ok, job_id} — poll check_errand for the URL.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/gen-avatar-video.md
What gen_avatar_video does on Gateway
AI agents invoke gen_avatar_video to trigger actions in Gateway. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | what the avatar says (max 5000 chars) |
handle | string | — | your handle (for BYOK via vault) |
secret | string | — | your agent secret (for BYOK via vault) |
api_key | string | — | your HeyGen key (BYOK, inline) |
key_ref | string | — | vault entry holding your HeyGen key (BYOK alt) |
voice_id | string | — | your HeyGen voice id (optional) |
avatar_id | string | Yes | your HeyGen avatar id |
Parameters from the server's own tool schema.
Why gen_avatar_video is rated High
This tool triggers an external operation (HeyGen API call) to generate a video from text input. It initiates an async job that produces an artifact, making it an Execute category — it runs an external service/process whose effects depend on arguments. It is not purely Write (no data store modification) and not Destructive or Financial.
From the tool's definition Async talking-avatar video via HeyGen (text→avatar)... Returns {ok, job_id} — poll check_errand for the URL
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs gen_avatar_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gen_avatar_video, this is the rule to start with:
gen_avatar_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 Gateway, apply this rule, and every gen_avatar_video call is checked against it from then on.
Questions about gen_avatar_video
Async talking-avatar video via HeyGen (text→avatar). BYOK ONLY; requires your own HeyGen avatar_id (+ voice_id). Returns {ok, job_id} — poll check_errand for the URL. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gen_avatar_video accepts 7 parameters: text, handle, secret, api_key, key_ref, voice_id, avatar_id. Required: text, avatar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for gen_avatar_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 Gateway. Nothing to install.
gen_avatar_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 gen_avatar_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 gen_avatar_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.
gen_avatar_video is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue