generate_asset_reference
Render an asset's reference image in the channel's art style — the visual anchor that keeps a character/environment looking identical across every shot. EVERY character, environment, and object asset needs one before generate_voiceover (the server enforces this; fire the jobs for all assets, then...
This record as markdown: /tools/com-framesail-framesail/generate-asset-reference.md
What generate_asset_reference does on Framesail
AI agents use generate_asset_reference 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 |
|---|---|---|---|
model | string | — | Image model ID; empty uses the server default for reference images |
asset_id | string | Yes | ID of the asset to render a reference image for, from list_assets |
settings | object | — | Model-specific settings (e.g. image quality/orientation); valid keys come from the model's settings_schema in list_models |
editable_sections | object | — | Per-call prompt section overrides, keyed by section name; see get_section_template for the reference-image job |
Parameters from the server's own tool schema.
Why generate_asset_reference is rated Medium
The tool creates new image assets and writes them to the database/storage (asset rows), which is a reversible data modification. While it triggers external rendering operations (similar to Execute), the primary effect is writing generated content to asset records. This is Write rather than Execute because the focus is on the persistent modification of asset data rather than executing arbitrary code.
From the tool's definition Generates and renders reference images that are written to asset rows. The description states 'the job writes the image onto the asset row' and the tool modifies asset data by adding visual reference content. This is a create/modify operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs generate_asset_reference 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 generate_asset_reference, this is the rule to start with:
generate_asset_reference 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 generate_asset_reference call is checked against it from then on.
Questions about generate_asset_reference
Render an asset's reference image in the channel's art style — the visual anchor that keeps a character/environment looking identical across every shot. EVERY character, environment, and object asset needs one before generate_voiceover (the server enforces this; fire the jobs for all assets, then one await_jobs). Async — the job writes the image onto the asset row: await_jobs(project_id), then list_assets and view_image the file_path to check likeness. 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.
generate_asset_reference accepts 4 parameters: model, asset_id, settings, editable_sections. 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 generate_asset_reference: 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.
generate_asset_reference 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 generate_asset_reference 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 generate_asset_reference. 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.
generate_asset_reference 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