create_tidal_playlist · TIDAL MCP: My Custom Picks MCP

WHAT IT DOES

What create_tidal_playlist does on TIDAL MCP: My Custom Picks

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

WHY IT NEEDS A POLICY

Why create_tidal_playlist needs a policy

Creating a playlist is a reversible modification operation (Write category). Severity is high because: (1) it modifies user account state on an external service (TIDAL), (2) an AI agent could create many playlists, clutter the user's account, or create playlists with misleading names/content, and (3) the action persists until manually deleted.

From the tool's definition Tool name is 'create_tidal_playlist' and server description states the tool enables users to 'create and manage playlists directly in their TIDAL account.' Sibling tools include 'delete_tidal_playlist' (destructive) and 'tidal_login' (execution), confirming…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_tidal_playlist Rate-limited

create_tidal_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_tidal_playlist": {
      "limits": [
        {
          "counter": "create_tidal_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: My Custom Picks, so you can run agents against it safely.

FAQ

Questions about create_tidal_playlist

What does the create_tidal_playlist tool do? +

create_tidal_playlist. It is categorised as a Write tool in the TIDAL MCP: My Custom Picks 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_tidal_playlist? +

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

What risk level is create_tidal_playlist? +

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

Can I rate-limit create_tidal_playlist? +

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

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

create_tidal_playlist is provided by the TIDAL MCP: My Custom Picks MCP server (mikeysrecipes/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.