explain_perfume_term
Explain perfume vocabulary and fragrance families: concentrations (EDC, EDT, EDP, extrait, elixir), sillage, projection, longevity, dry down, accord, top/heart/base notes, flanker, maceration, layering, niche vs designer, plus the 23 fragrance families (chypre, fougere, gourmand, oriental / amber...
This record as markdown: /tools/10ml-perfume-finder-mcp/explain-perfume-term.md
What explain_perfume_term does on Perfume Finder
AI agents call explain_perfume_term 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 |
|---|---|---|---|
term | string | — | A term or family. Examples: "EDP", "sillage", "chypre", "dry down", "fougere". Omit to list all terms. |
limit | integer | — | How many results per page (1-60, default 12). |
cursor | string | — | next_cursor from the previous page; omit for the first page. |
locale | string | — | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
Parameters from the server's own tool schema.
Why explain_perfume_term is rated Low
Even though explain_perfume_term 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs explain_perfume_term 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 explain_perfume_term, this is the rule to start with:
explain_perfume_term 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 explain_perfume_term call is checked against it from then on.
Questions about explain_perfume_term
Explain perfume vocabulary and fragrance families: concentrations (EDC, EDT, EDP, extrait, elixir), sillage, projection, longevity, dry down, accord, top/heart/base notes, flanker, maceration, layering, niche vs designer, plus the 23 fragrance families (chypre, fougere, gourmand, oriental / amber...) with their key notes and example perfumes. Use for 'what is the difference between EDT and EDP', 'what is a chypre', 'what does sillage mean'. Leave term empty to list everything covered. Not for individual notes (use explain_note). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
explain_perfume_term accepts 4 parameters: term, limit, cursor, locale. 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 explain_perfume_term: 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.
explain_perfume_term 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 explain_perfume_term 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 explain_perfume_term. 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.
explain_perfume_term 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