Search songs using neteasecli and return normalized NetEase track IDs.
AI agents call search_song to retrieve information from Netease Music without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries song data from NetEase Cloud Music to identify tracks matching search criteria. It has no side effects on the system or data state—it only reads and returns information. This is a classic Read category tool, with low severity since misuse would at worst return unwanted search results without operational impact.
From the tool's definition Tool performs search functionality returning track IDs without modifying any data. Description states 'Search songs...and return normalized NetEase track IDs' with no write, delete, or execution of arbitrary operations.
Documented attack patterns abuse exactly the kind of access search_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 search_song:
{
"version": "1",
"default": "deny",
"tools": {
"search_song": {}
}
}search_song is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search songs using neteasecli and return normalized NetEase track IDs. It is categorised as a Read tool in the Netease Music MCP Server, which means it retrieves data without modifying state.
Register the Netease Music MCP server in PolicyLayer and add a rule for search_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.
search_song is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_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 search_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.
search_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.