update_asset
Rename an asset and/or rewrite its description. If the look changed, regenerate its reference image afterwards so renders match.
This record as markdown: /tools/com-framesail-framesail/update-asset.md
What update_asset does on Framesail
AI agents use update_asset 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 |
|---|---|---|---|
name | string | — | New asset name; empty leaves the name unchanged |
asset_id | string | Yes | Asset ID, as returned by list_assets or create_asset |
description | string | — | New generation-facing look description; empty leaves it unchanged |
Parameters from the server's own tool schema.
Why update_asset is rated Medium
This tool modifies existing assets by updating their name, description, and reference images. These are reversible changes that alter data state without irreversibly deleting content or executing arbitrary code. The medium severity reflects that an AI agent could corrupt asset metadata or descriptions across a video production, potentially requiring manual cleanup, but the changes remain recoverable.
From the tool's definition Tool description states 'Rename an asset and/or rewrite its description' and 'regenerate its reference image', indicating modification of asset metadata and associated resources.
Attacks that exploit this kind of access
The rule that runs update_asset 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_asset, this is the rule to start with:
update_asset 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_asset call is checked against it from then on.
Questions about update_asset
Rename an asset and/or rewrite its description. If the look changed, regenerate its reference image afterwards so renders match. 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_asset accepts 3 parameters: name, asset_id, description. Required: asset_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_asset: 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_asset 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_asset 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_asset. 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_asset 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