Use this when the user needs to set up, log in, or troubleshoot neteasecli. It checks installation/login state and returns step-by-step commands Claude can guide the user through.
AI agents use setup_netease_login to create or update resources in Netease Music — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Netease Music environment.
This tool performs a write operation by creating/modifying login credentials and system configuration state for NetEase Cloud Music authentication. While it does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial), it does irreversibly establish authentication state that affects subsequent tool behavior.
From the tool's definition Tool description states it 'checks installation/login state' and 'returns step-by-step commands Claude can guide the user through', indicating it modifies system state by setting up authentication credentials and potentially installing or configuring software.
Documented attack patterns abuse exactly the kind of access setup_netease_login 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 setup_netease_login:
{
"version": "1",
"default": "deny",
"tools": {
"setup_netease_login": {
"limits": [
{
"counter": "setup_netease_login_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setup_netease_login stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Use this when the user needs to set up, log in, or troubleshoot neteasecli. It checks installation/login state and returns step-by-step commands Claude can guide the user through. It is categorised as a Write tool in the Netease Music MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Netease Music MCP server in PolicyLayer and add a rule for setup_netease_login: 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.
setup_netease_login is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup_netease_login 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 setup_netease_login. 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.
setup_netease_login 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.