New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERPerfume Finder SOURCE@10ml/perfume-finder-mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about explain_perfume_term

What does the explain_perfume_term tool do? +

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.

What parameters does explain_perfume_term accept? +

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.

How do I enforce a policy on explain_perfume_term? +

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.

What risk level is explain_perfume_term? +

explain_perfume_term is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit explain_perfume_term? +

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.

How do I block explain_perfume_term completely? +

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.

What MCP server provides explain_perfume_term? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Perfume Finder's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.