High Risk →

itunes_pause

Pause playback in Music (iTunes).

How to control itunes_pause ↓

What itunes_pause does on MCP-AppleMusic

AI agents invoke itunes_pause 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.

High Risk

Why itunes_pause needs a policy

This tool triggers an external operation (pausing Apple Music playback via AppleScript), which is an Execute-category action. It controls a running application but has no data read/write/destructive implications. Severity is low as the blast radius of misuse is minimal — it only pauses music playback.

From the tool's definition Pause playback in Music (iTunes)

Documented attack patterns abuse exactly the kind of access itunes_pause gives an agent:

How to control itunes_pause

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_pause:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "itunes_pause": {
      "limits": [
        {
          "counter": "itunes_pause_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register MCP-AppleMusic — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about itunes_pause

What does the itunes_pause tool do? +

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

How do I enforce a policy on itunes_pause? +

Register the MCP-AppleMusic MCP server in PolicyLayer and add a rule for itunes_pause: 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.

What risk level is itunes_pause? +

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

Can I rate-limit itunes_pause? +

Yes. Add a rate_limit block to the itunes_pause 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 itunes_pause completely? +

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

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

Enforce policy on every MCP-AppleMusic tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.