# 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 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).

Agent View of the PolicyLayer registry record for `find_similar_perfumes`. HTML page: https://policylayer.com/tools/10ml-perfume-finder-mcp/find-similar-perfumes

## Facts

- Tool: `find_similar_perfumes`
- Server: Perfume Finder (`@10ml/perfume-finder-mcp`) — https://policylayer.com/tools/10ml-perfume-finder-mcp.md
- Install: `npx -y @10ml/perfume-finder-mcp`
- Homepage: https://www.npmjs.com/package/@10ml/perfume-finder-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 11
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `house` | string | no | House of the perfume when the name alone is ambiguous, e.g. "Maison Francis Kurkdjian" |
| `limit` | integer | no | How many results per page (1-15, default 8). |
| `notes` | array | no | Known notes of the starting perfume, for perfumes outside the index. Example: ["jasmine","saffron","ambergris","cedar"] |
| `steer` | string | no | 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 | no | next_cursor from the previous page; omit for the first page. |
| `gender` | string | no | Only return perfumes for this audience (men and women include unisex) |
| `locale` | string | no | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
| `accords` | array | no | Known accords of the starting perfume. Example: ["amber","woody","sweet"] |
| `perfume` | string | no | 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 | no | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |
| `other_houses_only` | boolean | no | True to leave out perfumes from the same house as the starting perfume |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_similar_perfumes",
    "arguments": {}
  }
}
```

## 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 signals: High parameter count (11 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Perfume Finder:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_similar_perfumes": {}
  }
}
```

## Other tools on Perfume Finder (14)

- `compare_perfumes` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/compare-perfumes.md
- `explain_note` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/explain-note.md
- `explain_perfume_term` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/explain-perfume-term.md
- `find_gift` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/find-gift.md
- `find_perfume_alternatives` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/find-perfume-alternatives.md
- `get_house` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/get-house.md
- `get_perfume` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/get-perfume.md
- `list_houses` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/list-houses.md
- `perfumes_by_note` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/perfumes-by-note.md
- `pick_for_occasion` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/pick-for-occasion.md
- `recommend_perfumes` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/recommend-perfumes.md
- `search_guides` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/search-guides.md
- `search_perfumes` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/search-perfumes.md
- `suggest_layering` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/suggest-layering.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=10ml-perfume-finder-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/10ml-perfume-finder-mcp
