upload_song
Upload Music. Spends ElevenLabs credits.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/upload-song.md
What upload_song does on Elevenlabs
AI agents use upload_song to create or update resources in Elevenlabs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elevenlabs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_path | string | — | The audio file to upload. Local path. Required for this call. |
file_base64 | string | — | Base64 contents for "file". Use this when the server cannot read your local disk. |
file_filename | string | — | Filename to send for "file". Some endpoints infer the audio format from it. |
with_timestamps | boolean | — | Whether to transcribe the uploaded song and return word-level timestamps. If True, the response will include words_timestamps but will increase the latency. |
with_waveform_visual | boolean | — | Whether to return the visual waveform of the uploaded song. |
extract_composition_plan | boolean | — | Whether to generate and return the composition plan for the uploaded song. Pass a model id (`music_v1`, `music_v2` or `music_v2_5`) to control which composition |
Parameters from the server's own tool schema.
Why upload_song is rated Medium
An AI agent can call upload_song faster than any human can review: one bad instruction and it creates or modifies resources in Elevenlabs by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
The rule that runs upload_song safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_song, this is the rule to start with:
upload_song 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 Elevenlabs, apply this rule, and every upload_song call is checked against it from then on.
Questions about upload_song
Upload Music. Spends ElevenLabs credits. It is categorised as a Write tool in the Elevenlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
upload_song accepts 6 parameters: file_path, file_base64, file_filename, with_timestamps, with_waveform_visual, extract_composition_plan. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for upload_song: 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 Elevenlabs. Nothing to install.
upload_song 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 upload_song 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 upload_song. 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.
upload_song is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue