AI agents invoke whisper_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.
Installation tools execute system-level operations to download and install software packages. Given the context of a Voice Mode MCP server with a sibling tool 'get_whisper_version' and 'kokoro_install', this likely installs the Whisper ASR model/library onto the system. Installing software is an Execute-category action with high severity due to the potential for arbitrary code execution and system modification.
From the tool's definition Tool name 'whisper_install' implies installing software (Whisper speech recognition); description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access whisper_install gives an agent:
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_install:
{
"version": "1",
"default": "deny",
"tools": {
"whisper_install": {
"limits": [
{
"counter": "whisper_install_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} whisper_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.
Free to start. No card required.
whisper_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.
Register the Voice Mode MCP server in PolicyLayer and add a rule for whisper_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.
whisper_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the whisper_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.
Set action: deny in the PolicyLayer policy for whisper_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.
whisper_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.
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.