get_related_artists
Artists related to a seed artist — the drop-in for Spotify's removed GET /v1/artists/{id}/related-artists. No artist graph exists, so we derive one: build the seed artist's track-vector centroid, take its nearest catalogue tracks, aggregate by artist (each scored on its top-3 track similarities s...
This record as markdown: /tools/com-freqblog-music-metadata/get-related-artists.md
What get_related_artists does on FreqBlog Music Metadata
AI agents call get_related_artists to retrieve information from FreqBlog Music Metadata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Number of related artists to return (default 20). |
artist | string | Yes | Seed artist name (as it appears in the catalog; case-insensitive). |
Parameters from the server's own tool schema.
Why get_related_artists is rated Low
This tool performs a read-only query operation that searches a music catalog and returns metadata about related artists. There are no side effects, no data modifications, no code execution, and no irreversible operations. The computational work (building vectors, scoring) is internal processing that produces only informational output.
From the tool's definition Tool 'get_related_artists' retrieves and queries data: 'Returns `artist`, `count`, and `related`...' with no modification, deletion, or execution capabilities. It derives relationships and returns information for consumption.
Attacks that exploit this kind of access
The rule that runs get_related_artists safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FreqBlog Music Metadata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_related_artists, this is the rule to start with:
get_related_artists is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FreqBlog Music Metadata, apply this rule, and every get_related_artists call is checked against it from then on.
Questions about get_related_artists
Artists related to a seed artist — the drop-in for Spotify's removed GET /v1/artists/{id}/related-artists. No artist graph exists, so we derive one: build the seed artist's track-vector centroid, take its nearest catalogue tracks, aggregate by artist (each scored on its top-3 track similarities so a prolific artist can't dominate) plus a same-genre lift and a cross-genre penalty. Returns artist, count, and related (each {artist_name, score, match_count, sample_track_id}). Pass a sample_track_id straight to get_audio_features or suggest_next_track. Costs 2 quota units. It is categorised as a Read tool in the FreqBlog Music Metadata MCP Server, which means it retrieves data without modifying state.
get_related_artists accepts 2 parameters: limit, artist. Required: artist. The full parameter table on this page comes from the server's own tool schema.
Register the FreqBlog Music Metadata MCP server in PolicyLayer and add a rule for get_related_artists: 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 FreqBlog Music Metadata. Nothing to install.
get_related_artists 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_related_artists 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_related_artists. 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_related_artists is provided by the FreqBlog Music Metadata MCP server (https://mcp.freqblog.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FreqBlog Music Metadata, and thousands of servers like it.
This server
Across the catalogue