Get Spotify track details
AI agents call get_track_info to retrieve information from Multi-MCPs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a Spotify track (details such as artist, duration, release date, etc.) without modifying, creating, deleting, or executing any operations. It is a straightforward read operation with minimal risk—the worst misuse would be excessive querying, which has no destructive consequences. Severity is low due to the limited blast radius of information retrieval.
From the tool's definition Tool name 'get_track_info' and description 'Get Spotify track details' indicate a retrieval operation with no side effects. The verb 'Get' and the action of fetching track metadata from Spotify are characteristic of read-only queries.
Attacks that exploit this kind of access
Get Spotify track details. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.
Register the Multi-MCPs MCP server in PolicyLayer and add a rule for get_track_info: 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 Multi-MCPs. Nothing to install.
get_track_info 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_track_info 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_track_info. 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_track_info is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). 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 →