Stop current neteasecli/mpv playback and clear listening state.
AI agents invoke stop 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 executes a command that controls an external media player (mpv) and mutates application state. While not destructive (the action is reversible—playback can resume), it is an Execute category tool because it triggers external operations whose effects depend on the player's current state.
From the tool's definition Tool description states it will 'Stop current neteasecli/mpv playback and clear listening state' — this triggers an external operation (stopping playback) and modifies application state (clearing listening context).
Documented attack patterns abuse exactly the kind of access stop 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 stop:
{
"version": "1",
"default": "deny",
"tools": {
"stop": {
"limits": [
{
"counter": "stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop 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.
Stop current neteasecli/mpv playback and clear listening state. 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 stop: 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.
stop 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 stop 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 stop. 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.
stop 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.