カスタム辞書から指定した英単語のエントリを削除します。複数削除する場合はカンマ区切りで指定できます。
AI agents call remove_from_dictionary to permanently remove resources in Simple Voice MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes entries from the custom pronunciation dictionary. Deletion of data is irreversible, placing this in the Destructive category. However, the blast radius is low since it only affects a local pronunciation dictionary used for TTS, not critical data or systems.
From the tool's definition 削除します (deletes) — removes entries from the custom dictionary; deletion of dictionary entries is irreversible without a backup
Attacks that exploit this kind of access
カスタム辞書から指定した英単語のエントリを削除します。複数削除する場合はカンマ区切りで指定できます。. It is categorised as a Destructive tool in the Simple Voice MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Simple Voice MCP Server MCP server in PolicyLayer and add a rule for remove_from_dictionary: 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 Simple Voice MCP Server. Nothing to install.
remove_from_dictionary is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_from_dictionary 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 remove_from_dictionary. 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.
remove_from_dictionary is provided by the Simple Voice MCP Server MCP server (kurasuai-inc/voice-mcp). 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 →