High Risk →

whisper_model_install

whisper_model_install

How to control whisper_model_install ↓

What whisper_model_install does on Voice Mode

AI agents invoke whisper_model_install to trigger actions in Voice Mode. 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 whisper_model_install needs a policy

Based on the name, this tool likely downloads and installs a Whisper speech recognition model. Installation of software/models constitutes an Execute-level action as it runs an install process and modifies the local system state. Confidence is lowered due to the empty description.

From the tool's definition Tool name 'whisper_model_install' — description is empty and uninformative.

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

How to control whisper_model_install

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

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

whisper_model_install 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 Voice Mode — 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 whisper_model_install

What does the whisper_model_install tool do? +

whisper_model_install. It is categorised as a Execute tool in the Voice Mode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on whisper_model_install? +

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

What risk level is whisper_model_install? +

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

Can I rate-limit whisper_model_install? +

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

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

whisper_model_install is provided by the Voice Mode MCP server (mbailey/voicemode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Voice Mode tool call.

Start from Voice Mode, 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.

25 Voice Mode 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.