This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/emoji-lookup.md
What emoji_lookup does on UnClick
AI agents call emoji_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 |
|---|---|---|---|
query | string | Yes | Search term (e.g. heart, fire, smile). |
Parameters from the server's own tool schema.
Why emoji_lookup is rated Low
This tool performs a simple lookup or search operation to retrieve emoji data based on user input. It does not modify, delete, or execute any operations—it only retrieves and returns emoji information. This is a classic Read category tool with minimal security risk.
From the tool's definition Tool name 'emoji_lookup' and description 'Search emojis by name or keyword' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs emoji_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 emoji_lookup, this is the rule to start with:
emoji_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 emoji_lookup call is checked against it from then on.
Questions about emoji_lookup
Search emojis by name or keyword. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
emoji_lookup accepts 1 parameter: query. Required: query. 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 emoji_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.
emoji_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 emoji_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 emoji_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.
emoji_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