makeup_search
Search makeup products by brand, type, category, or tags.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/makeup-search.md
What makeup_search does on UnClick
AI agents call makeup_search 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 |
|---|---|---|---|
brand | string | — | Brand name (e.g. maybelline, covergirl, nyx) |
product_tags | string | — | Tags (e.g. vegan, organic, gluten_free) |
product_type | string | — | Product type (e.g. lipstick, foundation, mascara) |
product_category | string | — | Category (e.g. powder, cream, liquid) |
Parameters from the server's own tool schema.
Why makeup_search is rated Low
This tool retrieves or queries makeup product information based on search parameters (brand, type, category, tags). It has no capability to create, modify, delete, or execute operations—it is purely informational. The potential for misuse is minimal; incorrect search parameters would simply return irrelevant results or no results.
From the tool's definition Tool name 'makeup_search' and description 'Search makeup products by brand, type, category, or tags' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs makeup_search 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 makeup_search, this is the rule to start with:
makeup_search 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 makeup_search call is checked against it from then on.
Questions about makeup_search
Search makeup products by brand, type, category, or tags. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
makeup_search accepts 4 parameters: brand, product_tags, product_type, product_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 makeup_search: 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.
makeup_search 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 makeup_search 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 makeup_search. 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.
makeup_search 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