Open the MCP Apps voice panel when the client supports embedded UI.
AI agents invoke open_voice_panel to trigger actions in Pronunciation & Voice Coach. 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 action (opening a UI panel) in the client application, which constitutes executing an external operation. It doesn't read, write, or delete data, but it does cause a side effect by launching/displaying a UI component. Severity is low as the blast radius of misuse is minimal — it only opens a panel.
From the tool's definition 'Open the MCP Apps voice panel' — triggers an external UI operation in the client environment
Attacks that exploit this kind of access
Open the MCP Apps voice panel when the client supports embedded UI. It is categorised as a Execute tool in the Pronunciation & Voice Coach MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pronunciation & Voice Coach MCP server in PolicyLayer and add a rule for open_voice_panel: 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 Pronunciation & Voice Coach. Nothing to install.
open_voice_panel 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 open_voice_panel 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 open_voice_panel. 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.
open_voice_panel is provided by the Pronunciation & Voice Coach MCP server (pypi:mcp-server-pronunciation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →