add_to_playlist

Add a track to an existing playlist.

SERVERIconnect SOURCEiconnect-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/io-github-heznpc-iconnect/add-to-playlist.md

WHAT IT DOES

What add_to_playlist does on Iconnect

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

RISK

Why add_to_playlist is rated Medium

This tool modifies user music library data by adding a track to a playlist. It is a write operation—data is created or modified (the playlist's track list), but the action is reversible and causes no permanent loss of data. It has a narrow blast radius limited to a single user's music preferences. Severity is low because misuse would only add unwanted tracks to playlists, which can be easily undone.

From the tool's definition Tool name 'add_to_playlist' and description 'Add a track to an existing playlist' indicate creation/modification of playlist data. The action is reversible (tracks can be removed from playlists).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_to_playlist safely

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

add_to_playlist Rate-limited

add_to_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": {
    "add_to_playlist": {
      "limits": [
        {
          "counter": "add_to_playlist_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 Iconnect, apply this rule, and every add_to_playlist call is checked against it from then on.

FAQ

Questions about add_to_playlist

What does the add_to_playlist tool do? +

Add a track to an existing playlist. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_playlist? +

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

What risk level is add_to_playlist? +

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

Can I rate-limit add_to_playlist? +

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

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

add_to_playlist is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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