Low Risk

itunes_search

itunes_search

How to control itunes_search ↓

What itunes_search does on MCP-AppleMusic

AI agents call itunes_search to retrieve information from MCP-AppleMusic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why itunes_search needs a policy

Search operations retrieve data without side effects. No description is provided for this specific tool, which slightly reduces confidence, but the naming convention and context from sibling tools and server description clearly indicate this is a Read-category operation with minimal security risk.

From the tool's definition Tool name 'itunes_search' indicates a search operation. Sibling tools include 'itunes_library', 'itunes_all_songs', and 'itunes_current_song', which are clearly Read operations.

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

How to control itunes_search

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "itunes_search": {}
  }
}

itunes_search is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about itunes_search

What does the itunes_search tool do? +

itunes_search. It is categorised as a Read tool in the MCP-AppleMusic MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on itunes_search? +

Register the MCP-AppleMusic MCP server in PolicyLayer and add a rule for itunes_search: 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_search? +

itunes_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit itunes_search? +

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

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

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