update_caption_config
Merge a patch into the project's burned-in caption config (keys like enabled, plus styling). Read the current value from get_project (caption_config). Applies at the next export — no rebuild needed.
This record as markdown: /tools/com-framesail-framesail/update-caption-config.md
What update_caption_config does on Framesail
AI agents use update_caption_config 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 |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
caption_config | object | Yes | Partial caption config to merge (keys like enabled, plus styling); read the current value from get_project's caption_config |
Parameters from the server's own tool schema.
Why update_caption_config is rated Medium
This tool creates or modifies caption configuration settings within a video project. While the changes are reversible (the config can be patched again or reverted), this is a definitive update to project state that affects the final video output. It does not execute arbitrary code, delete data irreversibly, or move money, making Write the appropriate category.
From the tool's definition Tool description states it will 'Merge a patch into the project's burned-in caption config' and 'Applies at the next export', indicating modification of project configuration data.
Attacks that exploit this kind of access
The rule that runs update_caption_config 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_caption_config, this is the rule to start with:
update_caption_config 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_caption_config call is checked against it from then on.
Questions about update_caption_config
Merge a patch into the project's burned-in caption config (keys like enabled, plus styling). Read the current value from get_project (caption_config). Applies at the next export — no rebuild needed. 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_caption_config accepts 2 parameters: project_id, caption_config. Required: project_id, caption_config. 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_caption_config: 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_caption_config 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_caption_config 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_caption_config. 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_caption_config 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