Search for a song, play the best match with neteasecli/mpv, and return song info plus listening context. The style field is filled from NetEase song wiki when available.
AI agents invoke play_song to trigger actions in Netease Music. 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 searches for a song and then executes an external process (neteasecli/mpv) to play it. It triggers an external operation with real side effects (audio playback via a local application), placing it in the Execute category. Severity is medium because misuse could cause unwanted audio playback or resource consumption, but there is no data destruction or financial risk.
From the tool's definition 'play the best match with neteasecli/mpv' — triggers external media player execution to play audio
Documented attack patterns abuse exactly the kind of access play_song gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Netease Music, and nothing reaches the server without passing your rules. This is the rule we recommend for play_song:
{
"version": "1",
"default": "deny",
"tools": {
"play_song": {
"limits": [
{
"counter": "play_song_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Search for a song, play the best match with neteasecli/mpv, and return song info plus listening context. The style field is filled from NetEase song wiki when available. It is categorised as a Execute tool in the Netease Music MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Netease Music 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 Netease Music. 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 Netease Music MCP server (luuu-h/netease-music-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Netease Music, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Netease Music tools catalogued and risk-classified — across an index of 43,000+ MCP servers.