find_tracks_by_bpm

SERVERFreqBlog Music Metadata SOURCEhttps://mcp.freqblog.com/mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-freqblog-music-metadata/find-tracks-by-bpm.md

WHAT IT DOES

What find_tracks_by_bpm does on FreqBlog Music Metadata

AI agents call find_tracks_by_bpm 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
`bpm`	number	Yes	Target tempo in BPM.
`limit`	integer	—	Max tracks (default 10).
`tolerance`	number	—	Plus/minus BPM window (default 2).

Parameters from the server's own tool schema.

RISK

Why find_tracks_by_bpm is rated Low

This is a pure data retrieval operation that queries a music catalog by BPM (beats per minute) and returns matching track metadata. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It is a straightforward search/filter function, which falls under the Read category with low severity due to its limited blast radius if misused by an AI agent.

From the tool's definition Tool 'find_tracks_by_bpm' searches and returns catalog tracks matching a tempo criteria. The description explicitly states it 'Returns tracks' and is 'useful for DJ set planning, workout playlists, or tempo-matching.' No modification, deletion, execution of…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_tracks_by_bpm 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 find_tracks_by_bpm, this is the rule to start with:

find_tracks_by_bpm Allowed

find_tracks_by_bpm is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_tracks_by_bpm": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FreqBlog Music Metadata, apply this rule, and every find_tracks_by_bpm call is checked against it from then on.

FAQ

Questions about find_tracks_by_bpm

What does the find_tracks_by_bpm tool do? +

Find catalog tracks near a target tempo. Returns tracks whose BPM is within +/-tolerance of bpm, ordered by closeness then popularity — useful for DJ set planning, workout playlists, or tempo-matching. Each returned track carries full audio features. To also constrain by musical key, combine with find_tracks_by_key. It is categorised as a Read tool in the FreqBlog Music Metadata MCP Server, which means it retrieves data without modifying state.

What parameters does find_tracks_by_bpm accept? +

find_tracks_by_bpm accepts 3 parameters: bpm, limit, tolerance. Required: bpm. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on find_tracks_by_bpm? +

Register the FreqBlog Music Metadata MCP server in PolicyLayer and add a rule for find_tracks_by_bpm: 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.

What risk level is find_tracks_by_bpm? +

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

Can I rate-limit find_tracks_by_bpm? +

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

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

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

KEEP EXPLORING

More on FreqBlog Music Metadata, and thousands of servers like it.

This server

All 12 FreqBlog Music Metadata tools →

Across the catalogue

find_callees on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →