AI agents call search_music to retrieve information from Music MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from the user's music library without creating, modifying, or deleting any data. Searching is a pure read operation. The severity is low because even if misused by an AI agent, it only exposes existing music metadata without enabling any destructive or financial actions.
From the tool's definition Tool name is 'search_music' and description states 'Search the music library' — both indicate a query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access search_music 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 search_music:
{
"version": "1",
"default": "deny",
"tools": {
"search_music": {}
}
}search_music is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search the music library. It is categorised as a Read tool in the Music MCP MCP Server, which means it retrieves data without modifying state.
Register the Music MCP server in PolicyLayer and add a rule for search_music: 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.
search_music 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 search_music 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 search_music. 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.
search_music 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.