continue_last

SERVERSpotify SOURCE@novalux12/spotify-mcp

High RISK CLASS

Category Execute

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/continue-last.md

WHAT IT DOES

What continue_last does on Spotify

AI agents invoke continue_last to trigger actions in Spotify. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why continue_last is rated High

Triggers external Spotify playback operations with side effects on device state.

From the tool's definition Resume playback, 2-3 writes (play + shuffle/repeat best-effort)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs continue_last 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 continue_last, this is the rule to start with:

continue_last Rate-limited

continue_last stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "continue_last": {
      "limits": [
        {
          "counter": "continue_last_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about continue_last

What does the continue_last tool do? +

Resume the most recent saved playback position without knowing its name (newest by saved_at across the shared position store — a checkpoint_playback, a capture_playback_position bookmark or a save_playback_state slot). Pairs with checkpoint_playback. Quota: 2-3 writes (play + shuffle/repeat best-effort). It is categorised as a Execute tool in the Spotify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on continue_last? +

Register the Spotify MCP server in PolicyLayer and add a rule for continue_last: 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 continue_last? +

continue_last is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit continue_last? +

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

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

continue_last 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 538 Spotify tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →