// SCAN REPORT

Claud-Ear

24 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

3 can modify or destroy data

21 read-only

24 tools total

Community server · catalogue entry verified 30/06/2026

How to control Claud-Ear ↓

TOOL MAP

What Claud-Ear exposes to your agents

Read (21) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Claud-Ear tools

Write · Medium export_click_track Export operations typically create new files or data artifacts, qualifying as Write. Write · Medium export_stems Export operations create new files or data artifacts, making this a Write action. Write · Medium download_audio This tool fetches remote audio content and writes it to the local filesystem as a WAV file.

3 of Claud-Ear's 24 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Claud-Ear

PolicyLayer is an MCP gateway — it sits between your AI agents and Claud-Ear, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "download_audio": {
    "limits": [
      {
        "counter": "download_audio_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_audio": {
    "limits": [
      {
        "counter": "analyze_audio_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Claud-Ear — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CLAUD-EAR →

Instant setup, no code required.

FULL CATALOGUE

All 24 Claud-Ear tools

WRITE 3 tools

Write download_audio Download audio from a YouTube or SoundCloud URL as a WAV file. Write export_click_track export_click_track Write export_stems export_stems

READ 21 tools

Read analyze_audio analyze_audio Read analyze_for_songwriting analyze_for_songwriting Read analyze_section Analyze a specific section of an audio file. Useful for examining Read analyze_stems analyze_stems Read audio_query audio_query Read classify_genre Classify the genre of an audio file. Returns ranked genre predictions. Read classify_mood Detect the mood and emotional character of an audio file. Read compare_audio compare_audio Read deep_listen deep_listen Read detect_chords Detect the chord progression of a track. Uses Demucs to isolate the Read extract_melody Extract melodic content from a track. Uses Demucs to isolate the Read get_audio_info Get basic metadata about an audio file (duration, format, sample rate). Read get_library_suggestions get_library_suggestions Read get_song_structure Detect the structural sections of a song (intro, verse, chorus, etc.) Read identify_instruments Identify instruments and sound sources in an audio file. Read library_insights Return aggregate stats across the entire analyzed music library: Read query_library query_library Read search_and_download search_and_download Read similar_songs Find songs in the library that sound similar to the given WAV file. Read sync_tracks sync_tracks Read transcribe_lyrics transcribe_lyrics

FAQ

Questions about Claud-Ear

How do I prevent bulk modifications through Claud-Ear? +

The Claud-Ear server has 3 write tools including download_audio, export_click_track, export_stems. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Claud-Ear.

How many tools does the Claud-Ear MCP server expose? +

24 tools across 2 categories: Read, Write. 21 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Claud-Ear? +

Register the Claud-Ear MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Claud-Ear tool call.

Deterministic rules across all 24 Claud-Ear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CLAUD-EAR →

Instant setup, no code required.

24 Claud-Ear tools catalogued and risk-classified — across an index of 43,000+ MCP servers.