Get the user
AI agents call get_recently_played to retrieve information from Apple Music MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical playback data from the user's Apple Music account. It has no side effects, does not modify any data, and does not trigger external operations beyond querying stored information. It falls clearly into the Read category. Confidence is 0.85 rather than higher because the description is incomplete, but context from sibling tools strongly supports this classification.
From the tool's definition Tool name 'get_recently_played' and incomplete description 'Get the user' (likely 'Get the user's recently played tracks') indicate a retrieval operation.
Attacks that exploit this kind of access
Get the user. It is categorised as a Read tool in the Apple Music MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apple Music MCP Server MCP server in PolicyLayer and add a rule for get_recently_played: 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 Music MCP Server. Nothing to install.
get_recently_played is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_recently_played 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 get_recently_played. 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.
get_recently_played is provided by the Apple Music MCP Server MCP server (popand/applemusicmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →