Show which .voicemode.env files are being used for configuration. This shows the current configuration file discovery and loading order: - Global configuration from ~/.voicemode/voicemode.env - Project-specific configuration (searched up directory tree) - Current working directory for context Ret...
AI agents call show_config_files to retrieve information from Voice Mode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and displays configuration file paths and status. It retrieves existing state without side effects, matching the Read category pattern (list, get, fetch). The blast radius of misuse is minimal since reading configuration file locations poses no direct risk.
From the tool's definition Tool shows/displays configuration files and their discovery order. Description explicitly states 'Show which .voicemode.env files are being used' and 'Returns: Formatted list of configuration files and their status' — pure information retrieval with no…
Documented attack patterns abuse exactly the kind of access show_config_files 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 show_config_files:
{
"version": "1",
"default": "deny",
"tools": {
"show_config_files": {}
}
}show_config_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show which .voicemode.env files are being used for configuration. This shows the current configuration file discovery and loading order: - Global configuration from ~/.voicemode/voicemode.env - Project-specific configuration (searched up directory tree) - Current working directory for context Returns: Formatted list of configuration files and their status. It is categorised as a Read tool in the Voice Mode MCP Server, which means it retrieves data without modifying state.
Register the Voice Mode MCP server in PolicyLayer and add a rule for show_config_files: 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.
show_config_files is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the show_config_files 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 show_config_files. 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.
show_config_files 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.