list_music_tracks
List the project's background music tracks (volume, loop, timing).
This record as markdown: /tools/com-framesail-framesail/list-music-tracks.md
What list_music_tracks does on Framesail
AI agents call list_music_tracks 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_music_tracks is rated Low
This is a read operation that queries project data (music track metadata) to display to the user. No side effects, no data modification, no code execution, no destructive action. The blast radius of misuse is minimal — an agent could only retrieve information about music tracks already in the project.
From the tool's definition Tool is named 'list_music_tracks' and described as 'List the project's background music tracks (volume, loop, timing)' — it retrieves and displays information about existing music tracks without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs list_music_tracks 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_music_tracks, this is the rule to start with:
list_music_tracks 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_music_tracks call is checked against it from then on.
Questions about list_music_tracks
List the project's background music tracks (volume, loop, timing). It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
list_music_tracks 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_music_tracks: 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_music_tracks 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_music_tracks 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_music_tracks. 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_music_tracks 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