Execute music playback control commands
AI agents invoke execute_music_command to trigger actions in Music 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.
This tool runs playback control commands (play, pause, skip, etc.) via AppleScript, which are executable operations that trigger external state changes in the Apple Music application. While not destructive or financial, it has side effects that persist until reversed by another action.
From the tool's definition Tool name 'execute_music_command' and description 'Execute music playback control commands' indicate execution of control operations.
Documented attack patterns abuse exactly the kind of access execute_music_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Music MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_music_command:
{
"version": "1",
"default": "deny",
"tools": {
"execute_music_command": {
"limits": [
{
"counter": "execute_music_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_music_command 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.
Execute music playback control commands. It is categorised as a Execute tool in the Music MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Music MCP server in PolicyLayer and add a rule for execute_music_command: 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 Music MCP. Nothing to install.
execute_music_command 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 execute_music_command 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 execute_music_command. 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.
execute_music_command is provided by the Music MCP server (pedrocid/music-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Music MCP, 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.
6 Music MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.