list_scenes
List the project's scenes (composition layers, durations, layout).
This record as markdown: /tools/com-framesail-framesail/list-scenes.md
What list_scenes does on Framesail
AI agents call list_scenes 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 |
Parameters from the server's own tool schema.
Why list_scenes is rated Low
This tool queries and returns information about existing scenes in a video project (composition layers, durations, layout). It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes to the project state. The low severity reflects minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_scenes' and description 'List the project's scenes' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_scenes 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 list_scenes, this is the rule to start with:
list_scenes 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 list_scenes call is checked against it from then on.
Questions about list_scenes
List the project's scenes (composition layers, durations, layout). It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
list_scenes accepts 1 parameter: project_id. Required: 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 list_scenes: 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.
list_scenes 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 list_scenes 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 list_scenes. 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.
list_scenes 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