pick_for_occasion
Perfume picks for a moment: a season, an occasion (daytime, office, casual, evening, date night, special occasion), an audience and a style, each with the reason it fits. Use for 'a fresh summer office scent for men', 'date night perfume for her' or 'what to wear to a winter wedding'. Give at lea...
This record as markdown: /tools/10ml-perfume-finder-mcp/pick-for-occasion.md
What pick_for_occasion does on Perfume Finder
AI agents call pick_for_occasion to retrieve information from Perfume Finder 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 |
|---|---|---|---|
limit | integer | — | How many results per page (1-15, default 6). |
style | array | — | Styles wanted, e.g. ["fresh","clean"] for summer office wear |
cursor | string | — | next_cursor from the previous page; omit for the first page. |
gender | string | — | Audience the perfume is marketed to. men and women also include unisex perfumes. |
locale | string | — | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
season | string | — | Season the perfume suits (fall is accepted in text queries as autumn). |
occasion | string | — | Occasion the perfume suits: daytime, office, casual, evening, date night or special occasion. |
response_format | string | — | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |
Parameters from the server's own tool schema.
Why pick_for_occasion is rated Low
Even though pick_for_occasion only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs pick_for_occasion safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Perfume Finder, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pick_for_occasion, this is the rule to start with:
pick_for_occasion 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 Perfume Finder, apply this rule, and every pick_for_occasion call is checked against it from then on.
Questions about pick_for_occasion
Perfume picks for a moment: a season, an occasion (daytime, office, casual, evening, date night, special occasion), an audience and a style, each with the reason it fits. Use for 'a fresh summer office scent for men', 'date night perfume for her' or 'what to wear to a winter wedding'. Give at least one of season, occasion, gender or style. Not for taste-based matching (use recommend_perfumes), not for gifts (use find_gift) and not for classics (use search_perfumes with iconic true). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
pick_for_occasion accepts 8 parameters: limit, style, cursor, gender, locale, season, occasion, response_format. The full parameter table on this page comes from the server's own tool schema.
Register the Perfume Finder MCP server in PolicyLayer and add a rule for pick_for_occasion: 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 Perfume Finder. Nothing to install.
pick_for_occasion 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 pick_for_occasion 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 pick_for_occasion. 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.
pick_for_occasion is provided by the Perfume Finder MCP server (@10ml/perfume-finder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Perfume Finder, and thousands of servers like it.
This server
Across the catalogue