Low Risk

search_songs

Search Spotify tracks by query. Returns id, name, artist, image, url.

Accepts freeform code/query input (query)

Part of the Playlistable MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

lebrackyt/playlistable Read Risk 2/5

AI agents call search_songs to retrieve information from Playlistable without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_songs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

lebrackyt-playlistable.yaml
tools:
  search_songs:
    rules:
      - action: allow

See the full Playlistable policy for all 8 tools.

Tool Name search_songs
Category Read
Risk Level Low

Agents calling read-class tools like search_songs have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the search_songs tool do? +

Search Spotify tracks by query. Returns id, name, artist, image, url.. It is categorised as a Read tool in the Playlistable MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_songs? +

Add a rule in your Intercept YAML policy under the tools section for search_songs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Playlistable MCP server.

What risk level is search_songs? +

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

Can I rate-limit search_songs? +

Yes. Add a rate_limit block to the search_songs rule in your Intercept 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 search_songs completely? +

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

search_songs is provided by the Playlistable MCP server (lebrackyt/playlistable). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Playlistable

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.