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

search_perfumes

Search the 10ML Fragrance Index for perfumes by name, house, notes, accords, family, audience, season, occasion or style. Natural language works: 'fresh citrus summer scent for men' is understood. Set iconic to true for only the editors' iconic, era-defining classics ('must-know perfumes for her'...

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

This record as markdown: /tools/10ml-perfume-finder-mcp/search-perfumes.md

What search_perfumes does on Perfume Finder

AI agents call search_perfumes 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
house string — Only perfumes from this house. Examples: "Dior", "Maison Francis Kurkdjian", "MFK", "YSL"
limit integer — How many results per page (1-20, default 8).
query string — Free text: a perfume name, house, notes or mood. Examples: "fresh citrus summer for men", "Tom Ford tobacco", "vanilla gourmand for winter"
style string — A style word: aquatic, boozy, clean, creamy, dark, floral, fresh, citrusy, fruity, gourmand, green, leathery, musky, powdery, sensual, smoky, spicy, sweet, wood
cursor string — next_cursor from the previous page; omit for the first page.
family string — Fragrance family: fougere, chypre, oriental-amber, gourmand, aquatic, aromatic, woody, floral, white-floral, fruity, citrus, green, leather, oud, musky, powdery
gender string — Audience the perfume is marketed to. men and women also include unisex perfumes.
iconic boolean — true = only the editors' iconic, era-defining classics (works with every other filter, and without a query)
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).
accords array — Accords that must be present. Examples: ["woody","sweet"], ["fresh","aquatic"]
occasion string — Occasion the perfume suits: daytime, office, casual, evening, date night or special occasion.

Parameters from the server's own tool schema.

Why search_perfumes is rated Low

Even though search_perfumes 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.

Risk signalsHigh parameter count (15 properties)

Questions about search_perfumes

What does the search_perfumes tool do? +

Search the 10ML Fragrance Index for perfumes by name, house, notes, accords, family, audience, season, occasion or style. Natural language works: 'fresh citrus summer scent for men' is understood. Set iconic to true for only the editors' iconic, era-defining classics ('must-know perfumes for her', 'iconic winter scents'). Use when someone describes what they want or names a perfume or house and you need matching perfumes. Not for the full profile of one known perfume (use get_perfume), not for 'something like X' (use find_similar_perfumes) and not for dupes or alternatives to a famous perfume (use find_perfume_alternatives). Returns ranked perfumes with house, year, family, accords, key notes, an editorial character line and 10ml.com links. It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.

What parameters does search_perfumes accept? +

search_perfumes accepts 12 parameters: house, limit, query, style, cursor, family, gender, iconic, locale, season, accords, occasion. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_perfumes? +

Register the Perfume Finder MCP server in PolicyLayer and add a rule for search_perfumes: 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 search_perfumes? +

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

Can I rate-limit search_perfumes? +

Yes. Add a rate_limit block to the search_perfumes 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 search_perfumes completely? +

Set action: deny in the PolicyLayer policy for search_perfumes. 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 search_perfumes? +

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

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