create_asset
Manually add a character/environment/object the scan missed. asset_type: "character" | "environment" | "object". The description is the generation-facing spec of its look — be specific.
This record as markdown: /tools/com-framesail-framesail/create-asset.md
What create_asset does on Framesail
AI agents use create_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 | Yes | Asset name as the script refers to it (e.g. the character's name) |
asset_type | string | Yes | Kind of asset: "character", "environment", or "object" |
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
description | string | — | Generation-facing spec of the asset's look; every shot renders from it, so be specific |
Parameters from the server's own tool schema.
Why create_asset is rated Medium
This tool creates new assets within a video production project, adding visual elements that persist in the final output. It is reversible (assets can be removed or replaced in video editing workflows), making it Write rather than Destructive. The severity is medium because misuse could degrade video quality or introduce unwanted content, but the blast radius is limited to the single video project being edited.
From the tool's definition Tool description states 'Manually add a character/environment/object', which is a create operation that modifies the video composition by introducing new visual assets into the project.
Attacks that exploit this kind of access
The rule that runs create_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 create_asset, this is the rule to start with:
create_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 create_asset call is checked against it from then on.
Questions about create_asset
Manually add a character/environment/object the scan missed. asset_type: "character" | "environment" | "object". The description is the generation-facing spec of its look — be specific. 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.
create_asset accepts 4 parameters: name, asset_type, project_id, description. Required: name, asset_type, project_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 create_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.
create_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 create_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 create_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.
create_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