perfumes_by_note
List the perfumes in the 10ML Fragrance Index built around a note (vanilla, oud, bergamot, tonka bean, rose, iris, leather, sandalwood...), most prominent first, optionally only where the note sits in the top, heart or base, or for an audience, season or occasion. Spelling variants and other lang...
This record as markdown: /tools/10ml-perfume-finder-mcp/perfumes-by-note.md
What perfumes_by_note does on Perfume Finder
AI agents call perfumes_by_note 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 |
|---|---|---|---|
note | string | Yes | The note. Examples: "oud", "vanilla", "pink pepper", "Vanille" |
limit | integer | — | How many results per page (1-20, default 8). |
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. |
position | string | — | Where the note sits in the pyramid: top, heart, base or any |
response_format | string | — | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |
Parameters from the server's own tool schema.
Why perfumes_by_note is rated Low
Even though perfumes_by_note 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 perfumes_by_note 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 perfumes_by_note, this is the rule to start with:
perfumes_by_note 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 perfumes_by_note call is checked against it from then on.
Questions about perfumes_by_note
List the perfumes in the 10ML Fragrance Index built around a note (vanilla, oud, bergamot, tonka bean, rose, iris, leather, sandalwood...), most prominent first, optionally only where the note sits in the top, heart or base, or for an audience, season or occasion. Spelling variants and other languages work (agarwood finds oud, Vanille finds vanilla). Use for 'perfumes with oud', 'a vanilla scent for winter' or 'bergamot-forward colognes for men'. Not for explaining what a note smells like (use explain_note) and not for several notes at once (use search_perfumes with notes_include). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
perfumes_by_note accepts 9 parameters: note, limit, cursor, gender, locale, season, occasion, position, response_format. Required: note. 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 perfumes_by_note: 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.
perfumes_by_note 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 perfumes_by_note 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 perfumes_by_note. 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.
perfumes_by_note 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