# find_tracks_by_key

Find catalog tracks in a given musical key — for harmonic mixing and key-locked playlists. key accepts Camelot ("8A"), Open Key ("1m"), or a key name ("A-Minor", "F#-Major"). Returns tracks ordered by popularity, each with full audio features. To discover which keys mix well with a given key first, use find_compatible_keys.

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

## Facts

- Tool: `find_tracks_by_key`
- 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: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `key` | string | yes | Camelot ('8A'), Open Key ('1m'), or key name ('A-Minor', 'F#-Major'). |
| `limit` | integer | no | Max tracks (default 10). |

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_key",
    "arguments": {
      "key": "<key>"
    }
  }
}
```

## Why find_tracks_by_key is rated Low

This tool queries a music metadata catalog by musical key and returns matching track information. It performs a search/filter operation on existing data without side effects, side effects, or altering any state. The parameters (key format) are constrained to musical key specifications, and the output is informational (tracks with audio features). This is a straightforward Read operation with minimal risk of misuse.

From the tool's own definition: "Tool description states it 'Find[s] catalog tracks' and 'Returns tracks ordered by popularity' — purely retrieval operations with no modification, deletion, or execution of external commands."

## Use case

AI agents call find_tracks_by_key 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_key": {}
  }
}
```

## 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_bpm` — Read — https://policylayer.com/tools/com-freqblog-music-metadata/find-tracks-by-bpm.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