Create a new playlist with the given name and add tracks to it. 'songs' should be a comma-separated list of exact track names. Returns a confirmation message including the number of tracks added.
AI agents use itunes_create_playlist to create or update resources in MCP-AppleMusic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-AppleMusic environment.
This tool creates and modifies data (playlists and their contents) but does not delete, execute arbitrary code, process payments, or trigger external side effects beyond music library organization. Creating a playlist is reversible—it can be deleted. The blast radius of misuse is minimal: an agent could create unwanted playlists, but this causes no data loss, financial harm, or system compromise.
From the tool's definition Tool description states 'Create a new playlist' and 'add tracks to it', which are reversible write operations. The tool modifies the iTunes/Apple Music library by creating new data structures and relationships.
Documented attack patterns abuse exactly the kind of access itunes_create_playlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-AppleMusic, and nothing reaches the server without passing your rules. This is the rule we recommend for itunes_create_playlist:
{
"version": "1",
"default": "deny",
"tools": {
"itunes_create_playlist": {
"limits": [
{
"counter": "itunes_create_playlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}itunes_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.
Free to start. No card required.
Create a new playlist with the given name and add tracks to it. 'songs' should be a comma-separated list of exact track names. Returns a confirmation message including the number of tracks added. It is categorised as a Write tool in the MCP-AppleMusic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-AppleMusic MCP server in PolicyLayer and add a rule for itunes_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 MCP-AppleMusic. Nothing to install.
itunes_create_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the itunes_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.
Set action: deny in the PolicyLayer policy for itunes_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.
itunes_create_playlist is provided by the MCP-AppleMusic MCP server (kennethreitz/mcp-applemusic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-AppleMusic, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP-AppleMusic tools catalogued and risk-classified — across an index of 43,000+ MCP servers.