Reload configuration from .voicemode.env files and clear all caches. This tool reloads configuration from: 1. Global ~/.voicemode/voicemode.env file 2. Project-specific .voicemode.env files (searched up directory tree) 3. Environment variables (highest priority) Returns: Status message showing wh...
AI agents invoke config_reload 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.
This tool triggers an operational action (reloading config and clearing caches) rather than simply reading or writing data. It executes a runtime reconfiguration of the system state. While it reads config files, the primary effect is executing a reload/cache-clear operation. Severity is low since it only affects the voice mode configuration and cannot directly cause data loss or financial impact.
From the tool's definition Reload configuration from .voicemode.env files and clear all caches
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access config_reload 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 config_reload:
{
"version": "1",
"default": "deny",
"tools": {
"config_reload": {
"limits": [
{
"counter": "config_reload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}config_reload 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.
Reload configuration from .voicemode.env files and clear all caches. This tool reloads configuration from: 1. Global ~/.voicemode/voicemode.env file 2. Project-specific .voicemode.env files (searched up directory tree) 3. Environment variables (highest priority) Returns: Status message showing which files were loaded and any changes. 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 config_reload: 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.
config_reload 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 config_reload 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 config_reload. 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.
config_reload 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.