// SCAN REPORT

Claude Voice Notify

5 tools. 4 can modify or destroy data without limits.

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

Last updated: 12 Jun 2026

4 can modify or destroy data

1 read-only

5 tools total

Community server · catalogue entry verified 12/06/2026

How to control Claude Voice Notify ↓

TOOL MAP

What Claude Voice Notify exposes to your agents

Read (1) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Claude Voice Notify tools

Execute · Low notify_complete This tool triggers an auditory alert through an external TTS engine (VOICEVOX, Google Cloud TTS, or OpenAI), which constitutes executing an external operation. Execute · Medium notify_confirm The tool triggers an external TTS engine to produce audio output, which is an Execute-class action (external operation with side effects). Execute · Medium notify_speak This tool executes an external TTS engine to synthesize and play arbitrary audio output. Execute · Low notify_test The tool executes a test by invoking an external TTS engine to produce audio output ('reads aloud test successful').

4 of Claude Voice Notify's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Claude Voice Notify

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

Cap read operations

{
  "notify_list_providers": {
    "limits": [
      {
        "counter": "notify_list_providers_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 Claude Voice Notify — 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 CLAUDE VOICE NOTIFY →

Free to start. No card required.

FULL CATALOGUE

All 5 Claude Voice Notify tools

EXECUTE 4 tools

Execute notify_confirm 確認が必要なことを音声で通知する。メッセージ省略時は「確認をお願いします」と読み上げる。 Execute notify_speak 任意のテキストを音声で読み上げる。通知タイプ・速度・話者を指定可能。 Execute notify_test 音声通知の接続テストを実行する。「テスト成功」と読み上げる。 Execute notify_complete タスク完了を音声で通知する。メッセージ省略時は「タスクが完了しました」と読み上げる。

READ 1 tools

Read notify_list_providers 利用可能な音声プロバイダーの一覧を表示する。

FAQ

Questions about Claude Voice Notify

Is the Claude Voice Notify MCP server safe to use without restrictions? +

The Claude Voice Notify server is primarily read-only with 1 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Claude Voice Notify MCP server expose? +

5 tools across 2 categories: Read, Write. 1 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Claude Voice Notify? +

Register the Claude Voice Notify 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 Claude Voice Notify tool call.

Deterministic rules across all 5 Claude Voice Notify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CLAUDE VOICE NOTIFY →

Free to start. No card required.

5 Claude Voice Notify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.