# get_perfume

The full Fragrance Index profile of one perfume: house, launch year, audience, family, accords, note pyramid, best seasons and occasions, longevity, projection and perfumers (full profiles), the editors' character description, five similar perfumes, editorial alternatives from other houses when they exist, related 10ML guides and links. Use when you know which perfume is meant and need facts about it ('tell me about Aventus', 'what notes are in Delina'). Not for browsing (use search_perfumes), not for comparing two or more (use compare_perfumes). Unknown names return the closest matches.

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

## Facts

- Tool: `get_perfume`
- 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: 4 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `house` | string | no | House, when the name alone is ambiguous. Example: "Creed" |
| `locale` | string | no | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
| `perfume` | string | yes | A perfume by name, optionally with its house, e.g. "Baccarat Rouge 540", "Dior Sauvage", "Delina". An id from another tool also works, e.g. "creed-aventus". |
| `response_format` | string | no | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |

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

## Why get_perfume is rated Low

Even though get_perfume 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.

## Use case

AI agents call get_perfume 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": {
    "get_perfume": {}
  }
}
```

## 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
- `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
