List all available configuration keys with their descriptions. Returns: A formatted list of all VOICEMODE_* configuration keys and their purposes
AI agents call list_config_keys 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 tool retrieves and displays configuration information without side effects. It performs no modifications, deletions, code execution, or financial operations. The data returned is descriptive metadata about available configuration options, making it a straightforward Read operation with minimal risk if misused.
From the tool's definition Tool name 'list_config_keys' and description 'List all available configuration keys' indicate a retrieval operation that returns configuration metadata without modifying any state. The phrase 'Returns: A formatted list' confirms this is a query operation.
Documented attack patterns abuse exactly the kind of access list_config_keys 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 list_config_keys:
{
"version": "1",
"default": "deny",
"tools": {
"list_config_keys": {}
}
}list_config_keys 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.
List all available configuration keys with their descriptions. Returns: A formatted list of all VOICEMODE_* configuration keys and their purposes. 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 list_config_keys: 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.
list_config_keys 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 list_config_keys 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 list_config_keys. 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.
list_config_keys 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.