High Risk →

notify_complete

タスク完了を音声で通知する。メッセージ省略時は「タスクが完了しました」と読み上げる。

How to control notify_complete ↓

What notify_complete does on Claude Voice Notify

AI agents invoke notify_complete to trigger actions in Claude Voice Notify. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why notify_complete needs a policy

This tool triggers an auditory alert through an external TTS engine (VOICEVOX, Google Cloud TTS, or OpenAI), which constitutes executing an external operation. The blast radius is low since it only produces a voice notification with no data modification or destructive capability.

From the tool's definition 「タスク完了を音声で通知する」(notifies task completion via voice) — triggers an external TTS/audio operation

Documented attack patterns abuse exactly the kind of access notify_complete gives an agent:

How to control notify_complete

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "notify_complete": {
      "limits": [
        {
          "counter": "notify_complete_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

notify_complete stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Voice Notify — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about notify_complete

What does the notify_complete tool do? +

タスク完了を音声で通知する。メッセージ省略時は「タスクが完了しました」と読み上げる。. It is categorised as a Execute tool in the Claude Voice Notify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on notify_complete? +

Register the Claude Voice Notify MCP server in PolicyLayer and add a rule for notify_complete: 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 Claude Voice Notify. Nothing to install.

What risk level is notify_complete? +

notify_complete is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit notify_complete? +

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

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

notify_complete is provided by the Claude Voice Notify MCP server (kubouchiyuya/claude-voice-notify). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Voice Notify tool call.

Start from Claude Voice Notify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.