# recommend_perfumes

Personal perfume recommendations from taste: perfumes they love or dislike, notes they like or avoid, plus gender, season, occasion, style and family. Every pick says why (shared notes with a loved perfume, a liked note, fits the season). Use when someone says what they enjoy or avoid and wants suggestions ('I love Delina and vanilla, nothing too sweet, for winter evenings'). Not for one-off filters without taste (use search_perfumes), not for a single occasion list (use pick_for_occasion) and not for gifts (use find_gift).

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

## Facts

- Tool: `recommend_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: 12
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `likes` | array | no | Perfumes they love, e.g. ["Parfums de Marly Delina","Dior Sauvage"] |
| `limit` | integer | no | How many results per page (1-15, default 6). |
| `style` | array | no | Styles wanted, e.g. ["fresh","clean"] |
| `cursor` | string | no | next_cursor from the previous page; omit for the first page. |
| `family` | string | no | A fragrance family or word like "woody" or "citrus" |
| `gender` | string | no | Audience the perfume is marketed to. men and women also include unisex perfumes. |
| `locale` | string | no | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
| `season` | string | no | Season the perfume suits (fall is accepted in text queries as autumn). |
| `dislikes` | array | no | Perfumes they dislike; similar ones are pushed down |
| `occasion` | string | no | Occasion the perfume suits: daytime, office, casual, evening, date night or special occasion. |
| `liked_notes` | array | no | Notes they enjoy, e.g. ["vanilla","rose"] |
| `avoided_notes` | array | no | Notes to exclude entirely, e.g. ["patchouli","oud"] |

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": "recommend_perfumes",
    "arguments": {}
  }
}
```

## Why recommend_perfumes is rated Low

Even though recommend_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 (13 properties)

## Use case

AI agents call recommend_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": {
    "recommend_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
- `find_similar_perfumes` — Read — https://policylayer.com/tools/10ml-perfume-finder-mcp/find-similar-perfumes.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
- `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
