compose_detailed
Compose Music With A Detailed Response. Spends ElevenLabs credits.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/compose-detailed.md
What compose_detailed does on Elevenlabs
AI agents call compose_detailed to retrieve information from Elevenlabs 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 |
|---|---|---|---|
seed | number | null | — | |
prompt | string | null | — | |
model_id | string | — | |
finetune_id | string | null | — | |
lyrics_text | string | null | — | |
music_prompt | object | — | Composition plan for the `music_v1` model. Using this field with any other model will result in an error. |
output_format | string | — | Output format of the generated audio. Formatted as codec_sample_rate_bitrate. Use "auto" (the default) to let the API pick the best format for the selected mode |
sign_with_c2pa | boolean | — | Whether to sign the generated song with C2PA. Applicable only for mp3 files. |
generation_mode | object | — | |
music_length_ms | number | null | — | |
with_timestamps | boolean | — | Whether to return the timestamps of the words in the generated song. |
composition_plan | object | — |
Parameters from the server's own tool schema.
Why compose_detailed is rated Low
Even though compose_detailed only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs compose_detailed 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 compose_detailed, this is the rule to start with:
compose_detailed 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 Elevenlabs, apply this rule, and every compose_detailed call is checked against it from then on.
Questions about compose_detailed
Compose Music With A Detailed Response. Spends ElevenLabs credits. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
compose_detailed accepts 12 parameters: seed, prompt, model_id, finetune_id, lyrics_text, music_prompt, output_format, sign_with_c2pa, generation_mode, music_length_ms, with_timestamps, 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 compose_detailed: 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.
compose_detailed 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 compose_detailed 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 compose_detailed. 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.
compose_detailed 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