AI agents use generate_music to create or update resources in Portals — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portals environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text prompt describing the music (genre, mood, tempo, instruments, etc.). |
instrumental | boolean | — | If true, force an instrumental track with no vocals. |
duration_seconds | integer | — | Target duration in seconds. Defaults to 30. |
Parameters from the server's own tool schema.
This tool generates new audio content (a music track) from a text prompt and stores it, making it a Write operation. Severity is medium because: (1) the asset created could consume storage/API resources; (2) generated audio could potentially be misused for impersonation if vocal; (3) repeated calls could incur costs via ElevenLabs.
From the tool's definition Tool 'generate_music' uses ElevenLabs to create and return a URL to a newly generated audio file (MP3), which constitutes data creation.
Attacks that exploit this kind of access
Generate an instrumental or vocal music track from a text prompt using ElevenLabs. Returns a URL to the generated audio file (MP3). It is categorised as a Write tool in the Portals MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_music accepts 3 parameters: text, instrumental, duration_seconds. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Portals MCP server in PolicyLayer and add a rule for generate_music: 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 Portals. Nothing to install.
generate_music 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 generate_music 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 generate_music. 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.
generate_music is provided by the Portals MCP server (portals-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →