update_voice_block
Override one voice block's voice or playback volume (block ids from list_voice_blocks). Re-run generate_voiceover for the block afterwards if you changed its voice — existing audio is not regenerated automatically.
This record as markdown: /tools/com-framesail-framesail/update-voice-block.md
What update_voice_block does on Framesail
AI agents use update_voice_block to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
volume | object | — | Playback volume for this block, 0-1; omit to leave unchanged |
voice_id | string | — | New TTS voice ID for this block, from list_voices; empty leaves the voice unchanged |
voice_block_id | string | Yes | Voice block ID, from list_voice_blocks |
Parameters from the server's own tool schema.
Why update_voice_block is rated Medium
This tool updates voice block properties (voice type and volume level) within a video production system. It falls under Write because it modifies data reversibly—the changes can be undone by running update_voice_block again with different parameters.
From the tool's definition Override one voice block's voice or playback volume; the tool modifies existing voice block parameters (voice selection, playback volume) without deleting or executing external code.
Attacks that exploit this kind of access
The rule that runs update_voice_block safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_voice_block, this is the rule to start with:
update_voice_block stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every update_voice_block call is checked against it from then on.
Questions about update_voice_block
Override one voice block's voice or playback volume (block ids from list_voice_blocks). Re-run generate_voiceover for the block afterwards if you changed its voice — existing audio is not regenerated automatically. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_voice_block accepts 3 parameters: volume, voice_id, voice_block_id. Required: voice_block_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for update_voice_block: 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 Framesail. Nothing to install.
update_voice_block 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 update_voice_block 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 update_voice_block. 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.
update_voice_block is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue