music_play

Resume playback or play a track by id.

SERVERApple Apps MCP SOURCE0xatrilla/apple-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/0xatrilla-apple-mcp/music-play.md

WHAT IT DOES

What music_play does on Apple Apps MCP

AI agents invoke music_play to trigger actions in Apple Apps MCP. 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.

RISK

Why music_play is rated High

This tool executes an action on an external application (Apple Music), controlling playback state. It has no data read/write side effects and no financial or destructive consequences, but it does trigger an external operation whose effect depends on the argument (track id). Misuse potential is very low — worst case is unwanted audio playback.

From the tool's definition 'Resume playback or play a track by id' — triggers an external operation (controlling media playback) on the local macOS Music app

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs music_play safely

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

music_play Rate-limited

music_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "music_play": {
      "limits": [
        {
          "counter": "music_play_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apple Apps MCP, apply this rule, and every music_play call is checked against it from then on.

FAQ

Questions about music_play

What does the music_play tool do? +

Resume playback or play a track by id. It is categorised as a Execute tool in the Apple Apps MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on music_play? +

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

What risk level is music_play? +

music_play is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit music_play? +

Yes. Add a rate_limit block to the music_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.

How do I block music_play completely? +

Set action: deny in the PolicyLayer policy for music_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.

What MCP server provides music_play? +

music_play is provided by the Apple Apps MCP server (0xatrilla/apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apple Apps, and thousands of servers like it.

This server

All 19 Apple Apps tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →