play_playlist
Start playing a playlist by name, with optional shuffle control.
This record as markdown: /tools/heznpc-airmcp/play-playlist.md
What play_playlist does on AirMCP
AI agents invoke play_playlist to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why play_playlist is rated High
This tool executes a command to initiate music playback, which is an external operation with real-world effects (audio output, music service state change). It does not merely read data (so not Read), nor create/modify persistent data structures (so not Write or Destructive), nor involve financial transactions (so not Financial).
From the tool's definition Tool performs an action (starts playing) that triggers external operation (Apple Music playback) with effects that depend on arguments (playlist name, shuffle setting).
Attacks that exploit this kind of access
The rule that runs play_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 play_playlist, this is the rule to start with:
play_playlist stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 play_playlist call is checked against it from then on.
Questions about play_playlist
Start playing a playlist by name, with optional shuffle control. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for play_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.
play_playlist is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the play_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 play_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.
play_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