AI agents invoke itunes_play to trigger actions in MCP-AppleMusic. 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.
This tool executes an external command (play action) via AppleScript to control the macOS Music application. While the immediate impact is low (starting playback is reversible and non-destructive), it qualifies as Execute because it triggers an operation external to the MCP server itself.
From the tool's definition Tool performs 'Start playback in Music (iTunes)' — an action that triggers external operation (media playback control) whose effects depend on the current state of the music application and user's library.
Documented attack patterns abuse exactly the kind of access itunes_play 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_play:
{
"version": "1",
"default": "deny",
"tools": {
"itunes_play": {
"limits": [
{
"counter": "itunes_play_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} itunes_play 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.
Free to start. No card required.
Start playback in Music (iTunes). It is categorised as a Execute tool in the MCP-AppleMusic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP-AppleMusic MCP server in PolicyLayer and add a rule for itunes_play: 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_play 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 itunes_play 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_play. 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_play 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.