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'...
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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)
Attacks that exploit this kind of access
The rule that runs search_perfumes 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 search_perfumes, this is the rule to start with:
search_perfumes 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 search_perfumes call is checked against it from then on.
Questions about 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', '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.
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.
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.
search_perfumes 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 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.
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.
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.
This server
Across the catalogue