AI agents use suno_download_song to create or update resources in Suno MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Suno MCP environment.
This tool writes an MP3 file to the local filesystem. It retrieves data from Suno but its primary side effect is creating/writing a file on disk, making it a Write operation. Misuse could involve writing files to arbitrary locations, hence medium severity.
From the tool's definition Download a song MP3 to a specified folder
Attacks that exploit this kind of access
Download a song MP3 to a specified folder. It is categorised as a Write tool in the Suno MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Suno MCP server in PolicyLayer and add a rule for suno_download_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 Suno MCP. Nothing to install.
suno_download_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 suno_download_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 suno_download_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.
suno_download_song is provided by the Suno MCP server (unforced/suno-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 →