Critical Risk →

dictionary_remove

Remove a dictionary entry

How to control dictionary_remove ↓

What dictionary_remove does on VOICEPEAK MCP Server

AI agents call dictionary_remove to permanently remove resources in VOICEPEAK MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why dictionary_remove needs a policy

Removing a dictionary entry is an irreversible deletion of data (the pronunciation dictionary entry). While the blast radius is low (only affects TTS pronunciation mappings), the action cannot be undone without re-adding the entry manually, placing it in the Destructive category.

From the tool's definition Remove a dictionary entry

Documented attack patterns abuse exactly the kind of access dictionary_remove gives an agent:

How to control dictionary_remove

PolicyLayer is an MCP gateway — it sits between your AI agents and VOICEPEAK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dictionary_remove:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "dictionary_remove"
  ]
}

dictionary_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register VOICEPEAK MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about dictionary_remove

What does the dictionary_remove tool do? +

Remove a dictionary entry. It is categorised as a Destructive tool in the VOICEPEAK MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on dictionary_remove? +

Register the VOICEPEAK MCP Server MCP server in PolicyLayer and add a rule for dictionary_remove: 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 VOICEPEAK MCP Server. Nothing to install.

What risk level is dictionary_remove? +

dictionary_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dictionary_remove? +

Yes. Add a rate_limit block to the dictionary_remove 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.

How do I block dictionary_remove completely? +

Set action: deny in the PolicyLayer policy for dictionary_remove. 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.

What MCP server provides dictionary_remove? +

dictionary_remove is provided by the VOICEPEAK MCP Server MCP server (k2wanko/voicepeak-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VOICEPEAK MCP Server tool call.

Start from VOICEPEAK MCP Server, 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.

10 VOICEPEAK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.