This record as markdown: /tools/4shil-ytm-mcp/play-song.md
What play_song does on Ytm
AI agents invoke play_song to trigger actions in Ytm. 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.
Why play_song is rated High
This tool searches for and initiates playback of a song on an external service (YouTube Music). It executes an external operation whose effects depend on the arguments provided. It is not merely reading data, but actively controlling playback on a platform, placing it in the Execute category.
From the tool's definition 'Search and play a song on YouTube Music' — triggers external playback operation on YouTube Music
Attacks that exploit this kind of access
The rule that runs play_song safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ytm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For play_song, this is the rule to start with:
play_song stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ytm, apply this rule, and every play_song call is checked against it from then on.
Questions about play_song
Search and play a song on YouTube Music. It is categorised as a Execute tool in the Ytm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ytm MCP server in PolicyLayer and add a rule for play_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 Ytm. Nothing to install.
play_song 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 play_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 play_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.
play_song is provided by the Ytm MCP server (4shil/ytm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ytm, and thousands of servers like it.
This server
Across the catalogue