get_house
Profile of a perfume house: country, founded year, style (designer, niche, Middle Eastern, indie), what it is known for, its signature perfumes in the index and a link to explore it at 10ML. Understands nicknames (YSL, MFK, PDM, Paco Rabanne). Use for 'tell me about Creed', 'what is Amouage known...
This record as markdown: /tools/10ml-perfume-finder-mcp/get-house.md
What get_house does on Perfume Finder
AI agents call get_house 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 |
|---|---|---|---|
house | string | Yes | The house. Examples: "Creed", "YSL", "Maison Francis Kurkdjian", "Parfums de Marly" |
locale | string | — | Language of the 10ml.com links and labels. Perfume, house and note names stay as they are. |
response_format | string | — | concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection). |
Parameters from the server's own tool schema.
Why get_house is rated Low
Even though get_house 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.
Attacks that exploit this kind of access
The rule that runs get_house 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 get_house, this is the rule to start with:
get_house 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 get_house call is checked against it from then on.
Questions about get_house
Profile of a perfume house: country, founded year, style (designer, niche, Middle Eastern, indie), what it is known for, its signature perfumes in the index and a link to explore it at 10ML. Understands nicknames (YSL, MFK, PDM, Paco Rabanne). Use for 'tell me about Creed', 'what is Amouage known for' or 'best Dior perfumes'. Not for browsing all houses (use list_houses) and not for one perfume (use get_perfume). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
get_house accepts 3 parameters: house, locale, response_format. Required: house. 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 get_house: 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.
get_house 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 get_house 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 get_house. 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.
get_house 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