This record as markdown: /tools/heznpc-airmcp/create-playlist.md
What create_playlist does on AirMCP
AI agents use create_playlist to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why create_playlist is rated Medium
This tool creates a new playlist, which is a reversible write operation. The user can delete or modify playlists afterward. There are no irreversible destructive effects, financial consequences, or code execution involved. The blast radius is minimal—a playlist creation affects only the user's Music library and can be easily undone.
From the tool's definition Tool name 'create_playlist' and description 'Create a new playlist in Music' indicate creation of new data structure within Apple Music application.
Attacks that exploit this kind of access
The rule that runs create_playlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_playlist, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every create_playlist call is checked against it from then on.
Questions about create_playlist
Create a new playlist in Music. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air 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 AirMCP. Nothing to install.
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 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 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.
create_playlist is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue