// SCAN REPORT

Netease Music

13 tools. 9 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

9 can modify or destroy data

4 read-only

13 tools total

Community server · catalogue entry verified 11/06/2026

How to control Netease Music ↓

TOOL MAP

What Netease Music exposes to your agents

Read (4) Write / Execute (8) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Netease Music tools

Destructive · Medium shutdown The tool irreversibly terminates active playback, clears session state, and closes the web player server. Execute · Medium play_track This tool executes code/commands to trigger playback via external media players (neteasecli/mpv). Execute · Medium stop This tool executes a command that controls an external media player (mpv) and mutates application state. Execute · Medium open_web_player This tool starts a local web server and generates/serves a web UI, which constitutes executing an external operation (spinning up a server process and binding to a port).

9 of Netease Music's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Netease Music

PolicyLayer is an MCP gateway — it sits between your AI agents and Netease Music, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "shutdown": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "setup_netease_login": {
    "limits": [
      {
        "counter": "setup_netease_login_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_environment": {
    "limits": [
      {
        "counter": "check_environment_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Netease Music — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NETEASE MUSIC →

Free to start. No card required.

FULL CATALOGUE

All 13 Netease Music tools

DESTRUCTIVE 1 tools

Destructive shutdown Use this when the user asks to end the listening session, stop listening to music, close the player, or stop t

EXECUTE 7 tools

Execute play_track Play a NetEase numeric song ID with neteasecli/mpv and return song info plus the start listening context. The Execute stop Stop current neteasecli/mpv playback and clear listening state. Execute next_song Switch to another requested song by searching and playing it. Use this for natural-language Execute pause Pause current neteasecli/mpv playback. Execute play_song Search for a song, play the best match with neteasecli/mpv, and return song info plus listening context. The s Execute open_web_player Generate and serve a local web player UI for search/play/pause/stop and lyric context. Returns a localhost URL Execute resume Resume paused neteasecli/mpv playback.

WRITE 1 tools

Write setup_netease_login Use this when the user needs to set up, log in, or troubleshoot neteasecli. It checks installation/login state

READ 4 tools

Read check_environment Check neteasecli, mpv, and login status. Read get_listening_context Return the context that the AI should include on the next user message while music is playing. The lyric conte Read get_status Get current neteasecli/mpv playback status plus cached song metadata. Read search_song Search songs using neteasecli and return normalized NetEase track IDs.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Netease Music

Can an AI agent delete data through the Netease Music MCP server? +

Yes. The Netease Music server exposes 1 destructive tools including shutdown. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Netease Music? +

The Netease Music server has 1 write tools including setup_netease_login. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Netease Music.

How many tools does the Netease Music MCP server expose? +

13 tools across 3 categories: Execute, Read, Write. 4 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Netease Music? +

Register the Netease Music MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Netease Music tool call.

Deterministic rules across all 13 Netease Music tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NETEASE MUSIC →

Free to start. No card required.

13 Netease Music tools catalogued and risk-classified — across an index of 43,000+ MCP servers.