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

find_similar_perfumes

Find perfumes that smell like one the person already likes, ranked by shared notes, accords and style, each saying exactly what it shares and how close it is (very close, similar vibe, same spirit). Works from a perfume in the index (name and house, or id) OR from free notes/accords for any other...

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

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

What find_similar_perfumes does on Perfume Finder

AI agents call find_similar_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 — House of the perfume when the name alone is ambiguous, e.g. "Maison Francis Kurkdjian"
limit integer — How many results per page (1-15, default 8).
notes array — Known notes of the starting perfume, for perfumes outside the index. Example: ["jasmine","saffron","ambergris","cedar"]
steer string — Move away from the starting point in one direction: fresher, sweeter, darker, lighter, longer_lasting (needs a perfume in the index) or more_projection (same).
cursor string — next_cursor from the previous page; omit for the first page.
gender string — Only return perfumes for this audience (men and women include unisex)
locale string — Language of the 10ml.com links and labels. Perfume, house and note names stay as they are.
accords array — Known accords of the starting perfume. Example: ["amber","woody","sweet"]
perfume string — A perfume by name, optionally with its house, e.g. "Baccarat Rouge 540", "Dior Sauvage", "Delina". Or pass an id from another tool.
response_format string — concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection).
other_houses_only boolean — True to leave out perfumes from the same house as the starting perfume

Parameters from the server's own tool schema.

Why find_similar_perfumes is rated Low

Even though find_similar_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 (11 properties)

Questions about find_similar_perfumes

What does the find_similar_perfumes tool do? +

Find perfumes that smell like one the person already likes, ranked by shared notes, accords and style, each saying exactly what it shares and how close it is (very close, similar vibe, same spirit). Works from a perfume in the index (name and house, or id) OR from free notes/accords for any other perfume. Steer the result: fresher, sweeter, darker, lighter, longer_lasting or more_projection. Use for 'something like Baccarat Rouge 540', 'like Sauvage but fresher' or 'a perfume with notes of saffron and cedar'. Not for editorial dupes of a famous perfume from other houses (use find_perfume_alternatives) 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.

What parameters does find_similar_perfumes accept? +

find_similar_perfumes accepts 11 parameters: house, limit, notes, steer, cursor, gender, locale, accords, perfume, response_format, other_houses_only. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on find_similar_perfumes? +

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

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

Can I rate-limit find_similar_perfumes? +

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

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

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