# find_tracks_by_bpm

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.

Agent View of the PolicyLayer registry record for `find_tracks_by_bpm`. HTML page: https://policylayer.com/tools/com-freqblog-music-metadata/find-tracks-by-bpm

## Facts

- Tool: `find_tracks_by_bpm`
- Server: FreqBlog Music Metadata (`https://mcp.freqblog.com/mcp`) — https://policylayer.com/tools/com-freqblog-music-metadata.md
- Homepage: https://github.com/https://mcp.freqblog.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `bpm` | number | yes | Target tempo in BPM. |
| `limit` | integer | no | Max tracks (default 10). |
| `tolerance` | number | no | Plus/minus BPM window (default 2). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_tracks_by_bpm",
    "arguments": {
      "bpm": 0
    }
  }
}
```

## 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 own 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…"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FreqBlog Music Metadata:

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

## Other tools on FreqBlog Music Metadata (11)

- `build_setlist` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/build-setlist.md
- `find_compatible_keys` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/find-compatible-keys.md
- `find_tracks_by_key` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/find-tracks-by-key.md
- `get_audio_features` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/get-audio-features.md
- `get_audio_features_batch` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/get-audio-features-batch.md
- `get_recommendations` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/get-recommendations.md
- `get_related_artists` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/get-related-artists.md
- `score_transition` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/score-transition.md
- `search_catalog` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/search-catalog.md
- `suggest_next_track` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/suggest-next-track.md
- `tag_track` — Write — https://policylayer.com/tools/com-freqblog-music-metadata/tag-track.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-freqblog-music-metadata · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-freqblog-music-metadata