dictionary_lookup
Look up a word's definition, phonetics, and examples.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dictionary-lookup.md
What dictionary_lookup does on UnClick
AI agents call dictionary_lookup to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
word | string | Yes |
Parameters from the server's own tool schema.
Why dictionary_lookup is rated Low
This tool retrieves and queries dictionary data with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The blast radius of misuse is minimal—an AI agent could only retrieve dictionary information, posing no security risk.
From the tool's definition Tool description states 'Look up a word's definition, phonetics, and examples' — a pure retrieval operation with no modification, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs dictionary_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dictionary_lookup, this is the rule to start with:
dictionary_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every dictionary_lookup call is checked against it from then on.
Questions about dictionary_lookup
Look up a word's definition, phonetics, and examples. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
dictionary_lookup accepts 1 parameter: word. Required: word. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for dictionary_lookup: 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 UnClick. Nothing to install.
dictionary_lookup 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 dictionary_lookup 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 dictionary_lookup. 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.
dictionary_lookup is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue