AI agents invoke suno_wait_for_songs to trigger actions in Suno MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (music generation) and polls/waits for its completion, which are characteristic of Execute category actions. While music generation itself is benign, the tool commits computational resources and API calls based on provided parameters.
From the tool's definition Tool performs an asynchronous wait operation that blocks execution until external API (Suno) completes song generation.
Attacks that exploit this kind of access
Wait for songs to complete generation and return their URLs. It is categorised as a Execute tool in the Suno MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Suno MCP server in PolicyLayer and add a rule for suno_wait_for_songs: 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_wait_for_songs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the suno_wait_for_songs 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_wait_for_songs. 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_wait_for_songs 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 →