find_perfume_alternatives
The editors' alternatives (dupes) to a famous perfume from other houses: for each, why it is close and how close (very close, similar vibe, same spirit), plus the 10ML guide that compares them. Covers about 100 iconic originals such as Creed Aventus, Baccarat Rouge 540, Delina, Sauvage, Black Opi...
This record as markdown: /tools/10ml-perfume-finder-mcp/find-perfume-alternatives.md
What find_perfume_alternatives does on Perfume Finder
AI agents call find_perfume_alternatives 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 | — | House of the original when the name is ambiguous, e.g. "Parfums de Marly" |
limit | integer | — | How many results per page (1-10, default 6). |
cursor | string | — | next_cursor from the previous page; omit for the first page. |
locale | string | — | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
perfume | string | Yes | The famous perfume to find alternatives for. Examples: "Creed Aventus", "Baccarat Rouge 540", "Delina" |
closeness | string | — | Only alternatives at this closeness |
Parameters from the server's own tool schema.
Why find_perfume_alternatives is rated Low
Even though find_perfume_alternatives 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 find_perfume_alternatives 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 find_perfume_alternatives, this is the rule to start with:
find_perfume_alternatives 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 find_perfume_alternatives call is checked against it from then on.
Questions about find_perfume_alternatives
The editors' alternatives (dupes) to a famous perfume from other houses: for each, why it is close and how close (very close, similar vibe, same spirit), plus the 10ML guide that compares them. Covers about 100 iconic originals such as Creed Aventus, Baccarat Rouge 540, Delina, Sauvage, Black Opium or Santal 33. For other perfumes in the index the closest options from different houses are computed from notes and accords. Use for 'dupe of X', 'alternative to X', 'smells like X but from another house'. Not for general similarity inside the index (use find_similar_perfumes) and not for free-text discovery (use search_perfumes). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
find_perfume_alternatives accepts 6 parameters: house, limit, cursor, locale, perfume, closeness. Required: perfume. 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 find_perfume_alternatives: 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.
find_perfume_alternatives 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 find_perfume_alternatives 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 find_perfume_alternatives. 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.
find_perfume_alternatives 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