rename_account · Your Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_account does on Your Spotify MCP Server

AI agents use rename_account to create or update resources in Your Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Your Spotify MCP Server environment.

WHY IT NEEDS A POLICY

Why rename_account needs a policy

This tool creates or modifies data (username) in a reversible manner typical of Write category operations. It does not read sensitive data, execute external commands, destroy data irreversibly, or involve financial transactions. The low severity reflects minimal blast radius—a changed username is easily reverted and has no cascading consequences to user data or external systems.

From the tool's definition Tool description states 'Change your display username in Your Spotify', which is a reversible modification of user profile data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_account Rate-limited

rename_account 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_account": {
      "limits": [
        {
          "counter": "rename_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Your Spotify MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_account

What does the rename_account tool do? +

Change your display username in Your Spotify. This only affects your Your Spotify profile, not your actual Spotify account. Example queries: -. It is categorised as a Write tool in the Your Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_account? +

Register the Your Spotify MCP Server MCP server in PolicyLayer and add a rule for rename_account: 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 Your Spotify MCP Server. Nothing to install.

What risk level is rename_account? +

rename_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_account? +

Yes. Add a rate_limit block to the rename_account 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.

How do I block rename_account completely? +

Set action: deny in the PolicyLayer policy for rename_account. 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.

What MCP server provides rename_account? +

rename_account is provided by the Your Spotify MCP Server MCP server (pentafive/your-spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.