New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERPerfume Finder SOURCE@10ml/perfume-finder-mcp
Low RISK CLASS
Category Read
Parameters 80 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about pick_for_occasion

What does the pick_for_occasion tool do? +

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.

What parameters does pick_for_occasion accept? +

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.

How do I enforce a policy on pick_for_occasion? +

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.

What risk level is pick_for_occasion? +

pick_for_occasion is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pick_for_occasion? +

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.

How do I block pick_for_occasion completely? +

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.

What MCP server provides pick_for_occasion? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Perfume Finder's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.