get_whisper_version

THE RISK

Low Risk

Why get_whisper_version needs a policy

This tool retrieves static information (version number and installation status) without modifying any data, executing code, or triggering external operations. It is a straightforward Read operation with no side effects or blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_whisper_version' and description 'Get Whisper installation and version information' indicate a query operation that retrieves metadata about an installed component.

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

POLICY

How to control get_whisper_version

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 get_whisper_version:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_whisper_version": {}
  }
}

get_whisper_version is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Voice Mode — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Voice Mode tools

Destructive kokoro_uninstall Uninstall kokoro-fastapi and optionally remove models and data. This tool will: Destructive voice_statistics_reset Reset all voice conversation statistics and start a new session. Clears all track Destructive whisper_uninstall Uninstall whisper.cpp and optionally remove models and data. This tool will: Execute config_reload Reload configuration from .voicemode.env files and clear all caches. This tool re Execute kokoro_install kokoro_install Execute whisper_install whisper_install Execute whisper_model_install whisper_model_install Write refresh_provider_registry Manually refresh health checks for voice provider endpoints. Useful when a servic

All 25 Voice Mode tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_whisper_version

What does the get_whisper_version tool do? +

Get Whisper installation and version information. It is categorised as a Read tool in the Voice Mode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_whisper_version? +

Register the Voice Mode MCP server in PolicyLayer and add a rule for get_whisper_version: 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 get_whisper_version? +

get_whisper_version is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_whisper_version? +

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

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

get_whisper_version 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.

CHECK YOUR STACK →