Add a word to the personal dictionary
AI agents use add_to_dictionary to create or update resources in SpellChecker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpellChecker MCP Server environment.
This tool creates or modifies a personal dictionary by adding words. This is a reversible write operation (words can be removed later) with minimal blast radius—incorrect dictionary entries only affect spell-checking results, not critical data or system state. It does not read external data, execute code, delete irreversibly, or involve financial operations.
From the tool's definition Tool name 'add_to_dictionary' and description 'Add a word to the personal dictionary' clearly indicate creation/modification of dictionary data.
Attacks that exploit this kind of access
Add a word to the personal dictionary. It is categorised as a Write tool in the SpellChecker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SpellChecker MCP Server MCP server in PolicyLayer and add a rule for add_to_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 SpellChecker MCP Server. Nothing to install.
add_to_dictionary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_to_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 add_to_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.
add_to_dictionary is provided by the SpellChecker MCP Server MCP server (morahan/spellchecker-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 →