save_release_radar

SERVERSpotify SOURCE@novalux12/spotify-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/save-release-radar.md

WHAT IT DOES

What save_release_radar does on Spotify

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

RISK

Why save_release_radar is rated Medium

An AI agent can call save_release_radar faster than any human can review: one bad instruction and it creates or modifies resources in Spotify by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_release_radar safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_release_radar, this is the rule to start with:

save_release_radar Rate-limited

save_release_radar 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": {
    "save_release_radar": {
      "limits": [
        {
          "counter": "save_release_radar_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every save_release_radar call is checked against it from then on.

FAQ

Questions about save_release_radar

What does the save_release_radar tool do? +

Archive your Release Radar into a regular playlist (creates or overwrites the archive). Resolves Release Radar via /me/playlists exact match first, falling back to search (unverified); dry_run previews; idempotent if archive already matches. Result echoes source identity (owner, url, verified). It is categorised as a Write tool in the Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_release_radar? +

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

What risk level is save_release_radar? +

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

Can I rate-limit save_release_radar? +

Yes. Add a rate_limit block to the save_release_radar 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 save_release_radar completely? +

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

save_release_radar is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 544 Spotify tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →