get_segment_assets
List one segment's assets (images/video/overlays) including their status, config (prompts, model), and public URLs of rendered files — pass an image's public_url to view_image to actually look at it.
This record as markdown: /tools/com-framesail-framesail/get-segment-assets.md
What get_segment_assets does on Framesail
AI agents call get_segment_assets to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
segment_number | integer | Yes | 1-based segment number, as reported by get_segments |
Parameters from the server's own tool schema.
Why get_segment_assets is rated Low
This tool queries and retrieves metadata and URLs for assets within a video segment. It performs no creation, modification, deletion, or execution of operations. The tool simply returns information about existing assets and their configuration, which is a non-destructive read operation with minimal security risk.
From the tool's definition Tool description explicitly states 'List one segment's assets' and 'public URLs of rendered files', indicating data retrieval with no modification or side effects. The word 'List' is a classic Read operation.
Attacks that exploit this kind of access
The rule that runs get_segment_assets 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 get_segment_assets, this is the rule to start with:
get_segment_assets is read-only, so it stays allowed. 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 get_segment_assets call is checked against it from then on.
Questions about get_segment_assets
List one segment's assets (images/video/overlays) including their status, config (prompts, model), and public URLs of rendered files — pass an image's public_url to view_image to actually look at it. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
get_segment_assets accepts 2 parameters: project_id, segment_number. Required: project_id, segment_number. 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 get_segment_assets: 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.
get_segment_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_segment_assets 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 get_segment_assets. 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.
get_segment_assets 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