emojihub_by_category
Browse emojis by category (smileys, animals, food, etc.).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/emojihub-by-category.md
What emojihub_by_category does on UnClick
AI agents call emojihub_by_category 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 |
|---|---|---|---|
category | string | Yes | Category slug (e.g. smileys-and-people, animals-and-nature) |
Parameters from the server's own tool schema.
Why emojihub_by_category is rated Low
This tool queries and retrieves emoji data organized by category. It performs a read-only lookup operation with no side effects, no code execution, no data modification, and no financial impact. The lowest severity is appropriate as misuse would only return emoji information.
From the tool's definition Tool name and description indicate 'Browse emojis by category' - a retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
The rule that runs emojihub_by_category 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 emojihub_by_category, this is the rule to start with:
emojihub_by_category 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 emojihub_by_category call is checked against it from then on.
Questions about emojihub_by_category
Browse emojis by category (smileys, animals, food, etc.). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
emojihub_by_category accepts 1 parameter: category. Required: category. 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 emojihub_by_category: 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.
emojihub_by_category 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 emojihub_by_category 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 emojihub_by_category. 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.
emojihub_by_category 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