Return the context that the AI should include on the next user message while music is playing. The lyric context is the next 6 lyric lines at or after the current playback time.
AI agents call get_listening_context 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 queries and retrieves information about the currently playing track and its lyrics without modifying, executing, or deleting anything. It is purely informational, supporting the AI with context about the music playback state to enhance conversation continuity. The blast radius of misuse is minimal—returning incorrect or stale context data has no side effects on the music system or user data.
From the tool's definition Tool description states it 'Return[s] the context' and retrieves 'lyric context' for display. The verb 'Return' and lack of any modification language ('create', 'update', 'delete', 'execute') indicate a read-only operation that retrieves current playback…
Documented attack patterns abuse exactly the kind of access get_listening_context 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 get_listening_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_listening_context": {}
}
}get_listening_context 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.
Return the context that the AI should include on the next user message while music is playing. The lyric context is the next 6 lyric lines at or after the current playback time. 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 get_listening_context: 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.
get_listening_context 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 get_listening_context 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 get_listening_context. 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.
get_listening_context 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.