list_houses
Browse the perfume houses in the 10ML Fragrance Index with country, type (designer, niche, middle-eastern, indie, celebrity), perfumes profiled and what each is known for. Filter by type, country or a name fragment. Use when someone wants to explore brands, find niche or Middle Eastern houses, or...
This record as markdown: /tools/10ml-perfume-finder-mcp/list-houses.md
What list_houses does on Perfume Finder
AI agents call list_houses 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 |
|---|---|---|---|
type | string | — | Only houses of this type |
limit | integer | — | How many results per page (1-50, default 20). |
query | string | — | Part of a house name, e.g. "tom" or "maison" |
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. |
country | string | — | Only houses from this country, e.g. "France", "Italy", "United Arab Emirates" |
Parameters from the server's own tool schema.
Why list_houses is rated Low
Even though list_houses 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 list_houses 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 list_houses, this is the rule to start with:
list_houses 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 list_houses call is checked against it from then on.
Questions about list_houses
Browse the perfume houses in the 10ML Fragrance Index with country, type (designer, niche, middle-eastern, indie, celebrity), perfumes profiled and what each is known for. Filter by type, country or a name fragment. Use when someone wants to explore brands, find niche or Middle Eastern houses, or see which houses are covered. Not for one house's full profile (use get_house) and not for perfumes (use search_perfumes). It is categorised as a Read tool in the Perfume Finder MCP Server, which means it retrieves data without modifying state.
list_houses accepts 6 parameters: type, limit, query, cursor, locale, country. 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 list_houses: 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.
list_houses 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 list_houses 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 list_houses. 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.
list_houses 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