create_playlist · TIDAL MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_playlist does on TIDAL MCP Server

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

WHY IT NEEDS A POLICY

Why create_playlist needs a policy

Creating a playlist is a reversible write operation that modifies the user's account state by adding a new resource. It is not destructive (playlists can be deleted), not financial (no money involved), and not execute (no arbitrary code/commands). Severity is medium because misuse could clutter the user's account with unwanted playlists, but the impact is limited and easily remedied.

From the tool's definition Tool description states 'Create a new playlist in user's TIDAL account' — the verb 'Create' indicates data creation/modification. This is a write operation that adds a new resource to the user's account.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_playlist Rate-limited

create_playlist 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": {
    "create_playlist": {
      "limits": [
        {
          "counter": "create_playlist_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 TIDAL MCP Server, so you can run agents against it safely.

FAQ

Questions about create_playlist

What does the create_playlist tool do? +

Create a new playlist in user's TIDAL account. It is categorised as a Write tool in the TIDAL 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 create_playlist? +

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

What risk level is create_playlist? +

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

Can I rate-limit create_playlist? +

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

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

create_playlist is provided by the TIDAL MCP Server MCP server (keenanbb/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.