compare_perfumes
Compare 2 to 4 perfumes side by side: notes they share, notes only one has, accords, family, audience, launch year, longevity and projection, plus plain-language differences ('A is fresher, B is sweeter and lasts longer') and how close they are overall. Use when someone is choosing between named ...
This record as markdown: /tools/10ml-perfume-finder-mcp/compare-perfumes.md
What compare_perfumes does on Perfume Finder
AI agents call compare_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 |
|---|---|---|---|
locale | string | — | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
perfumes | array | Yes | 2 to 4 perfumes, each a name with optional house or an id. Example: ["Dior Sauvage","Tom Ford Ombre Leather"] |
response_format | string | — | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |
Parameters from the server's own tool schema.
Why compare_perfumes is rated Low
Even though compare_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.
Attacks that exploit this kind of access
The rule that runs compare_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 compare_perfumes, this is the rule to start with:
compare_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 compare_perfumes call is checked against it from then on.
Questions about compare_perfumes
Compare 2 to 4 perfumes side by side: notes they share, notes only one has, accords, family, audience, launch year, longevity and projection, plus plain-language differences ('A is fresher, B is sweeter and lasts longer') and how close they are overall. Use when someone is choosing between named perfumes or asks how two differ ('Sauvage vs Bleu', 'Delina or Layton'). Not for finding perfumes like one (use find_similar_perfumes) and not for one perfume's details (use get_perfume). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
compare_perfumes accepts 3 parameters: locale, perfumes, response_format. Required: perfumes. 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 compare_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.
compare_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 compare_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 compare_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.
compare_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